Ask Your Question
0

How to assign FIP from public network to container been built via magnum deployment (packstack) on RDO Ocata ?

asked 2017-02-25 11:30:48 -0600

jasonwg gravatar image

I was able successfully install via packstack (aio) magnum on RDO Ocata VM ( just pip install kubernets resolves original failure for magnum-conductor service) . In general, I have followed
http://egonzalez.org/magnum-in-rdo-op...
Starting at

magnum baymodel-create --name demoswarmbaymodel \
                       --image-id fedora-25-atomic-5 \
                       --keypair-id egonzalez \
                       --external-network-id public \
                       --dns-nameserver 8.8.8.8 \
                       --flavor-id testflavor \
                       --docker-volume-size 3  \
                       --coe swarm

Heat build succeeded and finally I got

[root@Server73 ~(keystone_admin)]# openstack stack list
+-------------------------+-------------------------+-----------------+----------------------+--------------+
| ID                      | Stack Name              | Stack Status    | Creation Time        | Updated Time |
+-------------------------+-------------------------+-----------------+----------------------+--------------+
| 8628e329-18ba-47b7      | demoswarmbay-           | CREATE_COMPLETE | 2017-02-25T16:11:05Z | None         |
| -9f1f-f86602330d83      | v3xyizyurdq3            |                 |                      |              |
+-------------------------+-------------------------+-----------------+----------------------+--------------+
[root@Server73 ~(keystone_admin)]# openstack server list
+--------------------------+--------------------------+--------+----------------------------+--------------------+
| ID                       | Name                     | Status | Networks                   | Image Name         |
+--------------------------+--------------------------+--------+----------------------------+--------------------+
| 34a2c253-e9d4-4e41-a07b- | de-5pnoa3pkb3r-0         | ACTIVE | =10.0.0.3, 192.168.122.108 | fedora-25-atomic-5 |
| 77622dbfcd89             | -7xq7px7hmcho-swarm-     |        |                            |                    |
|                          | node-t5hv24vcp6ys        |        |                            |                    |
| 6d35d2c7-a836-4693-bdde- | de-leq4gibwr-0           | ACTIVE | =10.0.0.5, 192.168.122.100 | fedora-25-atomic-5 |
| ec944bc68938             | -oylwvjisnetq-swarm-     |        |                            |                    |
|                          | master-5ckxd6abqohp      |        |                            |                    |
+--------------------------+--------------------------+--------+----------------------------+--------------------+
[root@Server73Centos ~(keystone_admin)]#

However, command magnum container-create looks to be deprecated in meantime, so container manually created via docker run -it .... gets standard IP 172.17.0.X ( ubuntu rastasheep was tested ) . Due to limited experience with magnum and kubernetes I don't see option to assign FIP from 192.168.122.0/24 to ubuntu container running on slave node
Second issue I have noticed is absence of httpd daemon on master, e.g. it is not clear how to get kubernetes console working

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-02-25 12:29:12 -0600

dbaxps gravatar image

updated 2017-02-26 13:52:05 -0600

Just using the field as comment

UPDATE 02/26/17
As of Newton release Magnum manage container's infra only
https://bugs.launchpad.net/magnum/+bu...
https://review.openstack.org/#/c/311476/
See also https://blueprints.launchpad.net/magn...
END UPDATE
Per http://egonzalez.org/magnum-in-rdo-op...
Command

magnum container-create --name demo-container \
                        --image docker.io/cirros:latest \
                        --bay demoswarmbay \
                        --command "ping -c 4 192.168.100.2"

is only pinging external gateway IP - 192.168.100.2
Mentioned blog does nothing except test container's outbound connectivity. It works fine on RDO Ocata Magnum implementation as well. Blog doesn't have any instructions regarding assigning FIP to container. Keeping in mind that "Nova-Docker" project was recently retired , magnum should provide some kind of mechanism (Neutron integrated ) to assign FIPs to containers,running inside for instance:- docker-swarm VMs on top of heat, to make them visible outside

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-02-25 11:30:48 -0600

Seen: 69 times

Last updated: Feb 26