contiv / contiv.github.io Goto Github PK

Hello,

When I am creating pods with infra network type in kubernetes. Below is the error I am getting in the logs.

Please help !

Warning  FailedCreatePodSandBox  1s (x3 over 3s)    kubelet, k8s-minion-2.ucsbang6.com  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "8ebcbc869429fd9f27406e3ad0511ed04f1d30ec95567b697677baa43aaec893" network for pod "http-deployment-7fdd7664c5-k2n2v": NetworkPlugin cni failed to set up pod "http-deployment-7fdd7664c5-k2n2v_default" network: Contiv:Error creating EP; Err: ovs operation failed. Error(s): [syntax error(Parsing ovsdb operation 1 of 3 failed: Type mismatch for member 'uuid-name'.)] [github.com/contiv/netplugin/drivers/ovsd.(*OvsdbDriver).performOvsdbOps ovsdbDriver.go 208]

Thanks in advance.

Arnab

In the example below?

In the ifconfig output, you will see that it would have created a veth virtual ethernet interface that could look like veth...... towards the end. More importantly it is allocated an IP address from default docker bridge docker0, likely 172.17.0.3 in this setup, and can be examined using

Shouldn't the IP be 172.17.0.5 not 172.17.0.3? The example boots a vanilla-c image which is assigned 172.17.0.5 under docker network inspect bridge in the example.

Different font sizes here.

make cluster and then running installer using cfg.yaml does not work. Procedure mentioned there does not specify about cfg.yaml.

Need to remove that stuff.

Per Kiran, description text should not be cobalt, too much blue

per Ceasar, add link to contiv training

The "Known issues" section in the Release Notes for Contiv 1.1 contains URLs pointing to a non-existent or hidden GitHub repo: https://github.com/contiv/ccn/issues/380, https://github.com/contiv/ccn/issues/383

Error

vagrant up
Ignoring nokogiri-1.6.3.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.3.1
Ignoring unf_ext-0.0.7.1 because its extensions are not built.  Try: gem pristine unf_ext --version 0.0.7.1
Bringing machine 'netplugin-node1' up with 'virtualbox' provider...
Bringing machine 'netplugin-node2' up with 'virtualbox' provider...
Bringing machine 'netplugin-node3' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The host path of the shared folder is missing: bin

http://contiv.github.io/documents/tutorials/container-101.html

http://contiv.github.io/documents/gettingStarted/networking/swarm.html

Here instead of export DOCKER_HOST=tcp://192.168.2.10:2375

now it should be export DOCKER_HOST=tcp://192.168.2.10:3375 as we are using docker 1.12 now.

Why do we have empty comments (//) https://github.com/contiv/contivmodel/blob/master/client/contivModelClient.go#L292 ? Lot of other objects do carry empty comments.

Current image is plain on both bottom and right sides. Can we use some image with borders on all sides in the home page so, it kind of isolates the image from other contents ?
@stacykor @akamkar What do you think?

I was trying the tutorial here https://kubernetes.io/docs/tasks/configure-pod-container/declare-network-policy/
and I could not get the DNS to work properly. I don't know if it is a problem of my machine of it is a bug. If I remember correctly the beta version of contiv used to replace the kube-dns with its own DNS, and don't know if that is still the case with the 1.0.0 and 1.0.1

Anyway the following are the commands and their output, which shows that the DSN is not working
root@master:/home/andrea# kubectl run nginx --image=nginx --replicas=2
deployment "nginx" created
root@master:/home/andrea# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-701339712-12j2l 0/1 ContainerCreating 0 10s
nginx-701339712-w8xnj 0/1 ContainerCreating 0 10s
vnf1-1793693912-lfm67 1/1 Running 2 1d
vnf2-1963301082-kf6dh 1/1 Running 2 1d
vnf2-1963301082-sc440 1/1 Running 2 1d
root@master:/home/andrea# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-701339712-12j2l 1/1 Running 0 20s
nginx-701339712-w8xnj 1/1 Running 0 20s
vnf1-1793693912-lfm67 1/1 Running 2 1d
vnf2-1963301082-kf6dh 1/1 Running 2 1d
vnf2-1963301082-sc440 1/1 Running 2 1d
root@master:/home/andrea# kubectl expose deployment nginx --port=80
service "nginx" exposed
root@master:/home/andrea# kubectl get svc,pod
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kubernetes 10.254.0.1 443/TCP 7d
svc/nginx 10.254.170.170 80/TCP 9s

NAME READY STATUS RESTARTS AGE
po/nginx-701339712-12j2l 1/1 Running 0 33s
po/nginx-701339712-w8xnj 1/1 Running 0 33s
po/vnf1-1793693912-lfm67 1/1 Running 2 1d
po/vnf2-1963301082-kf6dh 1/1 Running 2 1d
po/vnf2-1963301082-sc440 1/1 Running 2 1d
root@master:/home/andrea# kubectl run busybox --rm -ti --image=busybox /bin/sh
Waiting for pod default/busybox-3674381263-fthsn to be running, status is Pending, pod ready: false
Waiting for pod default/busybox-3674381263-fthsn to be running, status is Pending, pod ready: false
Waiting for pod default/busybox-3674381263-fthsn to be running, status is Pending, pod ready: false
Waiting for pod default/busybox-3674381263-fthsn to be running, status is Pending, pod ready: false
If you don't see a command prompt, try pressing enter.
/ # wget --spider --timeout=1 nginx
wget: bad address 'nginx'
/ #

Any suggestions?
Thank you so much!

For http://contiv.github.io/documents/tutorials/contiv-compose.html

In part (1), last step: change make demo to “make demo-swarm”

In part (3), add a note saying that this works and tested only on Linux.

In part(4), remove the information about running contiv-ui. It’s already running by default. Feel free to add a line saying that all the policies and other objects can be created using the UI as well.

All the volume related objects should be removed from https://godoc.org/github.com/contiv/contivmodel/client#Volume as its not related to our current release.

Also, Do we need volume related reference here ?
https://github.com/contiv/modelgen/blob/master/docs/contivModel.png

In procedure 1, There are no “demo-swarm” content in current Makefile.
http://contiv.github.io/documents/tutorials/contiv-compose.html

SKATSURA-M-R17N:~ skatsura$ cd deploy/src/github.com/contiv/
SKATSURA-M-R17N:contiv skatsura$ cd netplugin; make demo-swarm
make: *** No rule to make target `demo-swarm'.  Stop.

Blue sections in homepage http://contiv.github.io vary slightly. Is it expected ?

Can we create something similar like these tutorials , current ones are with docker swarm. We need same content but with k8s .

http://contiv.github.io/documents/tutorials/container-101.html
http://contiv.github.io/documents/tutorials/contiv-policy.html

In the "subnet IP pool" section of this page: http://contiv.github.io/documents/networking/ipam.html the example config is incorrect and leads to an error (ERRO[0000] subnet string invalid format):
netctl net create contiv-net -subnet 10.1.1.50-100/24

The correct syntax is:
netctl net create contiv-net -subnet 10.1.1.50-10.1.1.100/24
Creating network default:contiv-net

[vagrant@contiv-node3 ~]$ docker run -itd --name=contiv-c1 --net=contiv-net -e constraint:node=contiv-node3 alpine /bin/sh
docker: Error response from daemon: Unable to find a node that satisfies the following conditions
[available container slots].
See 'docker run --help'.

GET never returns password. This needs to be changed http://contiv.github.io/documents/api/contiv.html#auth_proxy_local_users__username__get

Also, here return object contains AuthzUUID http://contiv.github.io/documents/api/contiv.html#auth_proxy_authorizations_get

Contiv has the same font size as other items on this bar. Can we just make it little bigger and bold?

Also, can we add a logo as well there? something like https://kubernetes.io/docs/

@stacykor whatever you think is the best.

Spacing between the rows in reference section is much more than other sections. Please ignore if its not a big deal.

The blue color of text links is too light and doesn't have enough contrast. It failed the accessibility test. Please replace it with #036e97.
Also, if could we use dark gray (#5c5d61 ) for text to differentiate the text from links?

Following things need to be added.
Whatever content goes in for these issues

1: contiv/install#49
2: contiv/install#46
3: https://github.com/contiv/install/blob/master/QUICKSTART.md
4: https://github.com/contiv/install/blob/master/README.md
5: https://github.com/contiv/install/blob/master/install/ansible/install_swarm.sh

Please feel free to add more details.

In the discussion of service load balancing (documents/networking/services.md): first part of example creates a network 'contiv-srv-net' with a set of labels. Second part creates a network 'contiv-net' with no labels and attaches labeled service containers to that network. This doesn't seem to make sense. Are the two examples supposed to be related? What's the correct sequence of commands?

Quick Start should cover only the following scenarios:

Install prereqs (latest of vagrant/virtualbox/vboxsf, make, git)
a. vagrant plugin install vagrant-vbguest
git pull contiv/install
make demo-k8s
a. make cluster
b. curl
c. untar
d. run install.sh with k8s on the vagrant cluster.
e. take them to UI on the setup
Provide instructions on running a few contiv demos on this setup, and explain what each does.
Repeat 3 for docker swarm.

http://contiv.github.io/documents/admin/index.html

Need to add content for the Docker Compose and Kubernetes entries in the Examples menu. Currently they lead to the Examples page containing the Nomad and multicast examples.

Here both GET gives the same information. Do we need this redundant buttons ? Also, this occupies extra space. Its better to remove the section that's displayed when the API link is clicked.

When open the url "http://contiv.github.io/install/netplugin/extras/sample_cfg.yml ", browser tells me "Page Not Found".

http://contiv.github.io/documents/networking/ipam.html

please do required changes , considering we have now embedded DNS. Also please provide clear set of steps to test IPAM.

Per Rohit reduce font size for tutorials

Please add this here http://contiv.github.io/documents/admin/manageAuthorizations.html under Authorizing Users

Active Directory(AD) users are authorized based on the authorizations defined on their AD groups in our system.
Single user can be associated with many AD groups (one of them being the primary group) and 
the authorizations can be defined on any of them expect the primary group.
Because, there is no straight-froward mechanism to retrieve user's primary group from AD. 

More details here: http://lists.freeradius.org/pipermail/freeradius-users/2012-August/062055.html