[Rdo-list] [Heat][ceilometer] vertical scalability
by ICHIBA Sara
Hey there,
I know that performing horizontal scalability in Openstack can be automated
with heat and ceilometer. I'm wondering if we can do the same thing for
vertical scalability with these two modules?
B.regards,
Sara
9 years, 6 months
[Rdo-list] reconsidering midstream repos
by Hugh O. Brock
Seems like the midstream repos are causing us a lot of pain with little
gain, at least in some cases. (For example it appears the t-h-t
midstream exists to carry a single patch that enables mongodb on
Centos.) Is it worth discussing whether we can eliminate some of these,
especially for upstreams like t-h-t that aren't tightly tied to the
OpenStack release schedule?
/me ducks flying bricks
--Hugh
--
== Hugh Brock, hbrock(a)redhat.com ==
== Senior Engineering Manager, Cloud Engineering ==
== RDO Manager: Install, configure, and scale OpenStack ==
== http://rdoproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey
9 years, 6 months
[Rdo-list] RDO + floating IPs
by Tomas Sedovic
Hey everyone,
I tried to get RDO set up with floating IP addresses, but I'm running
into problems I'm not sure how to debug (not that familiar with
networking and Neutron).
I followed these guides on a clean Fedora 21 x86_64 server:
https://www.rdoproject.org/Quickstart
https://www.rdoproject.org/Floating_IP_range
This on a baremetal box in a network outside of my control but in which
there are 5 extra IP addresses assigned to me. It's quite possible that
I'm missing something or doing something wrong, so here's exactly what I
did:
yum update -y && reboot
---
systemctl disable NetworkManager
systemctl enable network
systemctl stop NetworkManager && ifdown enp0s25 && systemctl start network
yum install -y https://rdo.fedorapeople.org/rdo-release.rpm
yum install -y openstack-packstack
yum-config-manager --disable openstack-kilo
yum-config-manager --enable openstack-kilo-testing
setenforce 0
packstack --allinone --provision-all-in-one-ovs-bridge=n
--os-heat-install=y --os-ceilometer-install=y
That succeeded, so I added a keypair and made sure the "default"
security group allows all traffic.
So next onto the neutron stuff:
source /root/keystonerc_admin
neutron net-create mynetwork --router:external
(got a new network with type vxlan and id
4a30e2cc-b9f3-4ebd-b7ab-c35e38c3c75c)
For the subnet I need the CIDR, gateway and the floating IP range. I'm
not sure if I'm getting these right:
* CIDR: `ip addr`, find my network interface (enp0s25), get it's inet
value: 10.40.128.44/20
* Gateway: `ip route | grep default` -> default via 10.40.143.254 dev
enp0s25
* And these 5 IP addresses are assigned to me: 10.40.128.80-10.40.128.84
neutron subnet-create mynetwork 10.40.128.44/20 --name mysubnet
--enable_dhcp=False --allocation_pool
start=10.40.128.80,end=10.40.128.84 --gateway 10.40.143.254
(this creates a subnet with id 2e3d6966-a659-454c-8c38-d98ed3f105e5)
neutron router-create myrouter
(this creates a router with id fced82e6-9917-4053-a286-02838d0325fc)
neutron router-gateway-set fced82e6-9917-4053-a286-02838d0325fc
4a30e2cc-b9f3-4ebd-b7ab-c35e38c3c75c
(myrouter id and mynetwork id)
neutron floatingip-create mynetwork
With all that out of the way, I created another network+subnet for my
VMs and added a myrouter's interface to it. Then I launched a cirros VM
into that network and associated a floating IP from "mynetwork".
The VM had some trouble with cloud-init:
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending select for 192.168.0.4...
Lease of 192.168.0.4 obtained, lease time 86400
cirros-ds 'net' up at 0.66
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 0.66. request failed
failed 2/20: up 5.67. request failed
failed 3/20: up 8.67. request failed
failed 4/20: up 11.67. request failed
...
once all 20 requests failed, it got to a login screen, but I could not
ping or SSH into it:
# ping 10.40.128.81
PING 10.40.128.81 (10.40.128.81) 56(84) bytes of data.
From 10.40.128.44 icmp_seq=1 Destination Host Unreachable
From 10.40.128.44 icmp_seq=2 Destination Host Unreachable
From 10.40.128.44 icmp_seq=3 Destination Host Unreachable
From 10.40.128.44 icmp_seq=4 Destination Host Unreachable
# ssh cirros(a)10.40.128.81
ssh: connect to host 10.40.128.81 port 22: No route to host
Does anyone have any idea what I may be doing wrong?
Thanks,
Tomas
9 years, 6 months
[Rdo-list] RDO-Manager ovecloud change existing plan, how?
by Pedro Sousa
Hi all,
I've deployed rdo-manager in a virt env and everything is working fine
except the vnc console which is alreday an open bug for that.
Now I would like to change some parameters on my deployment, let's say I
wan't to disable NeutronTunneling, I wan't to use VLAN for tenants and use
1500 MTU on dnsmasq.
So I downloaded the plan:
#tuskar plan-templates -O /tmp uuid
changed plan.yaml, environment.yaml, provider-Controller-1.yaml,
provider-Compute-1.yaml.
than I ran the stack:
# heat stack-create -f tmp/plan.yaml -e tmp/environment.yaml overcloud
The overcloud is deployed fine but the values aren't changed. What I'm
missing here?
Thanks,
Pedro Sousa
9 years, 6 months
[Rdo-list] introspection and raid configuration
by Imre Farkas
Hi all,
I would like to gather some feedback on the current worfklow regarding
the subject. RAID configuration on DRAC machines works as follows (it
assumes there's no RAID volume on the machine):
1. user defines the deployment profile and the target raid configuration
for each profile
2. ironic-discoverd introspects the node to gather facts
3. ach-match picks a deployment profile based on the gathered facts
4. instack triggers the raid configuration based on the selected profile
A bug[1] has been discovered regarding step 2: ironic-discoverd fails
because it tries to figure out the size of the local disk but it can't
find any as no volume exists on the RAID controller yet. This is a
chicken-and-egg problem because ironic-discoverd doesn't work if the
RAID volume(s) has not been configured but the RAID configuration can't
be triggered if ironic-discoverd hasn't gathered the facts about the node.
Few possible workarounds:
#1: make saving the local disk size optional in the standard plugin in
ironic-discoverd. The downside is that the standard plugin is supposed
to enroll nodes in ironic with all attributes necessary for scheduling.
This assumption might fail with this solution.
#2: run discovery multiple times with different set of plugins. The run
before RAID configuration would exclude the standard plugin while the
run afterwards could potentially exclude others. The parameters passed
by the user to ironic-discoverd for each run need to be properly
documented. It would slow down the installation because each run
requires a reboot which takes a lot of time on bare metal.
#3: name your suggestion!
Any thoughts/preference on the above described workarounds?
Thanks,
Imre
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1222124
9 years, 6 months
[Rdo-list] [horizon] can't access the dashboard
by ICHIBA Sara
Hello there,
I recently installed openstack kilo with packstack. The dashboard was
working fine until I rebooted My machine, here I couldn't any more access
the dashboard and I had the error that says to contact the administrator
for more details.
I googled my issue with horizon and found somewhere on that the problem is
related to OPENSTACK-KEYSTONE_DEFAULT_ROLE and they suggested to define it
as admin. I did, but my problem is still persisting. I enabled debug mode
and here I got this errors in the browser after a failed attemp to login to
my dashboard.
In advance, thanks for your response.
Sara
ValidationError at /auth/login/
[u'La valeur \xab\xa0cdf7ff7189174b64983c9bd3e128099c\xa0\xbb doit
\xeatre un nombre entier.']
Request Method: POST Request URL:
http://192.168.5.34/dashboard/auth/login/ Django Version: 1.8.1 Exception
Type: ValidationError Exception Value:
[u'La valeur \xab\xa0cdf7ff7189174b64983c9bd3e128099c\xa0\xbb doit
\xeatre un nombre entier.']
Exception Location:
/usr/lib/python2.7/site-packages/django/db/models/fields/__init__.py
in to_python, line 969 Python Executable: /usr/bin/python Python Version:
2.7.5 Python Path:
['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
'/usr/lib64/python27.zip',
'/usr/lib64/python2.7',
'/usr/lib64/python2.7/plat-linux2',
'/usr/lib64/python2.7/lib-tk',
'/usr/lib64/python2.7/lib-old',
'/usr/lib64/python2.7/lib-dynload',
'/usr/lib64/python2.7/site-packages',
'/usr/lib/python2.7/site-packages',
'/usr/share/openstack-dashboard/openstack_dashboard']
Server time: ven, 22 Mai 2015 12:52:22 +0000
9 years, 6 months
[Rdo-list] No ironic pkg during packsack installation
by idzzy
Hello,
I'm trying to setup Kilo in three nodes (controller, compute, network).
During packstack installation, following error message was output.
---------------------------------
10.32.37.47_ironic.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]
ERROR : Error appeared during Puppet run: 10.32.37.47_ironic.pp
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-ironic-conductor' returned 1: Error: No matching Packages to list
You will find full trace in log /var/tmp/packstack/20150526-164515-bTdbtG/manifests/10.32.37.47_ironic.pp.log
Please check log file /var/tmp/packstack/20150526-164515-bTdbtG/openstack-setup.log for more information
---------------------------------
Please see these logs from this link.
/var/tmp/packstack/20150526-164515-bTdbtG/manifests/10.32.37.47_ironic.pp.log
=> https://www.dropbox.com/s/bdnu7aujwom97zg/10.32.37.47_ironic.pp.log?dl=0
/var/tmp/packstack/20150526-164515-bTdbtG/openstack-setup.log
=> https://www.dropbox.com/s/aysqstzjdlpweam/openstack-setup.log?dl=0
openstack-kilo and epel repo has been already added.
---------------------------------
# yum repolist | awk '{print $1}'
base/7/x86_64
epel/x86_64
extras/7/x86_64
openstack-kilo
updates/7/x86_64
---------------------------------
But seems to not find openstack-ironic-* pkg
---------------------------------
# yum search openstack-ironic
Warning: No matches found for: openstack-ironic
No matches found
---------------------------------
Relevant bug (already fixed) https://bugzilla.redhat.com/show_bug.cgi?id=1187343
There are ironic puppet modules.
---------------------------------
# ll /usr/share/openstack-puppet/modules/ironic/
total 40
drwxr-xr-x 2 root root 4096 May 26 16:01 examples
-rw-r--r-- 1 root root 758 May 16 00:36 Gemfile
drwxr-xr-x 3 root root 4096 May 26 16:01 lib
-rw-r--r-- 1 root root 10143 May 16 00:36 LICENSE
drwxr-xr-x 5 root root 4096 May 26 16:01 manifests
-rw-r--r-- 1 root root 1312 May 16 00:36 metadata.json
-rw-r--r-- 1 root root 303 May 16 00:36 Rakefile
-rw-r--r-- 1 root root 1751 May 16 00:36 README.md
---------------------------------
How fix this issue? Any ides would be helpful for me.
I’m also asking this to ask.openstack.org.
https://ask.openstack.org/en/question/67465/rdo-kilo-no-pkg-of-ironic-con...
Thank you.
—
idzzy
9 years, 6 months
