Ask Your Question

TripleZ's profile - activity

2019-02-06 13:34:18 -0500 received badge  Student (source)
2019-01-29 03:37:05 -0500 received badge  Notable Question (source)
2018-11-28 00:13:42 -0500 received badge  Popular Question (source)
2018-10-25 04:18:15 -0500 received badge  Popular Question (source)
2018-09-18 08:21:41 -0500 commented answer Adding compute node to an existing openstack environment

Yep, I have checked my version is Ocata.

2018-09-17 09:38:59 -0500 asked a question How to set a subnet as the default ip allocation net?

I have a network called "external" which has two subnets "external-public" and "external-share". Here are the subnets information:

  • external-public: 211.65.102.0/24 | start ip: 211.65.102.42, end ip: 211.65.102.54
  • external-share : 10.10.0.0/16 | start ip: 10.10.0.100, end ip: 10.10.255.254

I want to configure the machines (instances, routers, floating IPs etc.) to allocate the IPs in the external-share instead of external-public . However, it always allocate an IP in the external-public for me.

I can allocate an IP with a specific subnet via the OpenStack CLI client. But I wonder that is there a way to do this via horizon dashboard ? Or is there any way to set the subnet become the network "default" subnet ?

2018-09-17 09:38:55 -0500 asked a question The VMs cannot access the Internet after installing the OpenStack via Kolla-ansible

Here are the networks in my clusters.

https://i.redd.it/v599767o0th11.png (image description)

I have successfully deployed the OpenStack via the kolla-ansible tool. However, when I ran over the init-runonce script, I found the VM cannot access to the Internet.

Here are the network info in the Controller node:

[root@Controller01 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:f2:e9:c7:4f:ca brd ff:ff:ff:ff:ff:ff
    inet 211.65.102.41/24 brd 211.65.102.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::2052:2312:8fb4:e5dd/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 40:f2:e9:c7:4f:cb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::42f2:e9ff:fec7:4fcb/64 scope link
       valid_lft forever preferred_lft forever
4: ens6f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0e:1e:b9:4f:a0 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.41/24 brd 10.0.0.255 scope global ens6f0
       valid_lft forever preferred_lft forever
    inet 10.0.0.254/32 scope global ens6f0
       valid_lft forever preferred_lft forever
    inet 211.65.102.70/32 scope global ens6f0
       valid_lft forever preferred_lft forever
    inet6 fe80::f0a5:bac4:b28b:e059/64 scope link
       valid_lft forever preferred_lft forever
5: ens6f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0e:1e:b9:4f:a2 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.41/24 brd 10.1.0.255 scope global ens6f1
       valid_lft forever preferred_lft forever
    inet6 fe80::3f05:a32:63fb:eec5/64 scope link
       valid_lft forever preferred_lft forever
6: enp0s20u1u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 42:f2:e9:c7:4f:cf brd ff:ff:ff:ff:ff:ff
7: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:bc:1e:8c:ef brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:bcff:fe1e:8cef/64 scope link
       valid_lft forever preferred_lft forever
168: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d6:f8:ee:1d:5e:5d brd ff:ff:ff:ff:ff:ff
169: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 40:f2:e9:c7 ...
(more)
2018-09-17 09:38:17 -0500 commented answer Adding compute node to an existing openstack environment

Why my kolla-ansible cannot use the option --limit?

2018-09-04 06:48:38 -0500 received badge  Enthusiast
2018-09-04 06:48:38 -0500 received badge  Enthusiast
2018-08-23 04:22:41 -0500 received badge  Famous Question (source)
2018-08-23 04:22:41 -0500 received badge  Notable Question (source)
2018-08-23 04:22:41 -0500 received badge  Popular Question (source)
2017-12-20 07:13:02 -0500 answered a question nova-manage cell_v2: error: argument action: invalid choice: 'create_cell' (choose from 'discover_hosts', 'map_cell0', 'map_cell_and_hosts', 'map_instances', 'simple_cell_setup', 'verify_instance'

I have the exact same issue as you, have you solved it ?

2017-12-20 07:13:02 -0500 asked a question Ocata Nova cell_v2
[root@Controller triplez]# su -s /bin/sh -c "nova-manage cell_v2 create_cell --name-cell1 --verbose" nova
usage: nova-manage cell_v2 [-h]

                       {discover_hosts,map_cell0,map_cell_and_hosts,map_instances,simple_cell_setup,verify_instance}
                       ...
nova-manage cell_v2: error: argument action: invalid choice: 'create_cell' (choose from 'discover_hosts', 'map_cell0', 'map_cell_and_hosts', 'map_instances', 'simple_cell_setup', 'verify_instance')

Why it said that there is no "create_cell" option?

My OpenStack version is Ocata and here is my nova components versions:

openstack-nova-api.noarch         1:15.0.8-1.el7         @centos-openstack-ocata
openstack-nova-common.noarch      1:15.0.8-1.el7         @centos-openstack-ocata
openstack-nova-conductor.noarch   1:15.0.8-1.el7         @centos-openstack-ocata
openstack-nova-console.noarch     1:15.0.8-1.el7         @centos-openstack-ocata
openstack-nova-novncproxy.noarch  1:15.0.8-1.el7         @centos-openstack-ocata
openstack-nova-placement-api.noarch
openstack-nova-scheduler.noarch   1:15.0.8-1.el7         @centos-openstack-ocata
2017-12-20 07:13:02 -0500 answered a question `nava-manage cell_v2` do not have `create_cell` arguments.

I have the same question, have you solved this?

2017-12-19 06:21:15 -0500 received badge  Supporter (source)