Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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

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-openstack-liberty-manual-installation-from-source-code/
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