[Rdo-list] [package announce] openstack clients update
by Pádraig Brady
Havana RDO client packages have been updated as follows:
python-neutronclient-2.3.1-2 -> 2.3.1-3
Fix incompatibility with neutron-2013.2.2 http://pad.lv/1277120
python-swiftclient-1.8.0 -> python-swiftclient-2.0.2
Remove multipart/form-data file upload
Fix --insecure option on auth
Port to python-requests
Fix swiftclient help
Install manpage in share/man/man1 instead of man/man1
Add capabilities option
Install swiftclient manpage
Add --object-name
retry on ratelimit
Fix help of some optional arguments
Enable usage of proxies defined in environment (http(s)_proxy).
Don't crash when header is value of None
Fix download bandwidth for swift command.
Allow custom headers when using swift download (CLI)
Add close to swiftclient.client.Connection
enhance swiftclient logging
Clarify main help for post subcommand
Fixes python-swiftclient debugging message
Add verbose output to all stat commands
Skip sniffing and reseting if retry is disabled
user defined headers added to swift post queries
Extend usage message for `swift download`
python-novaclient-2.15.0 -> 2.16.0
Invalid client version message unclear
Fix i18n messages in novaclient, part II
Update broken command line reference link
Remove invalid parameter of quota-update
Adds support for the get_rdp_console API
Fixed polling after boot in shell
Fix Serivce class AttributeError
[UT] Fixed floating_ip_pools fake return to expected one
[UT] Removed duplicate key from dict in fake baremetal_node
Flavor ExtraSpecs containing '/' cannot be deleted
Fix i18n messages in novaclient, part I
Adds ability to boot a server via the Nova V3 API
Removes unsupported volume commands from V3 API support
Fix logic for "nova flavor-show 0#"
Don't call CS if a token + URL are provided
Adds volume support for the V3 API
Fixes ambiguous cli output between "None" and NoneType
Support list deleted servers for admin
Using floating-ip-{associate|disassociate}
Adds quota usage support for the V3 API
Fix tab-completion of --flags under OS X
Remove class_name parameter from quota_class
Ensure that the diagnostics are user friendly
Added v3 interfaces in reference doc
Generate interfaces reference doc
Ensure that nova client prints dictionaries and arrays correctly
Allow empty response in service-list
Nova aggregate-details should be more human friendly
Adding additional tests for novaclient ssh
Fix "device" as the optional para on volume-attach
Adds simple tenant usage support for the Nova V3 API
Adds keypairs support for the Nova V3 API
Adds certificates support for Nova V3 API
Adds aggregates support for Nova V3 API
Adds hypervisor support for Nova V3 API
Adds services support for Nova V3 API
Adds second part of quotas support for Nova V3 API
Adds first part of quotas support for Nova V3 API
Adds availability zone support for Nova V3 API
Adds basic servers support for the Nova V3 API
add support for nova ssh user@host
Allow multiple volume delete from cli like Cinder
Expose the rebuild preserve-ephemeral extension
Stop using deprecated keyring backends
Adds images support for Nova V3 API
Remove commands not supported by Nova V3 API
Adds agent support for Nova V3 API
Adds flavor access support for Nova V3 API
Adds flavor support for Nova V3 API
Allow graceful shutdown on Ctrl+C
add support for server set metadata item
Fix incorrect help message on flavor_access action
Sets default service type for Nova V3 API
Adds a --show option to the image-create subcommand
Allows users to retrieve ciphered VM passwords
Removes unnecessary pass
nova security-group-* should support uuid as input
Flatten hypervisor-show dictionary for printing
Print security groups as a human readable list
Adds locking to completion caches
Make 'nova ssh' automatically fall back to private address
Quote URL in curl output to handle query params
Add --insecure to curl output if required
Remove deprecated NOVA_RAX_AUTH
Print dicts in alphabetical order
Make os-cache retry on an invalid token
Document and make OS_CACHE work
Add shelve/unshelve/shelve-offload command
if we have a valid auth token, use it instead of generating a new one
Fix AttributeError in Keypair._add_details()
Make nova CLI use term "server" where possible
Novaclient shell list command should support a minimal server list
Add v3 HostManager
10 years, 1 month
[Rdo-list] Fwd: Re: Fwd: Re: Canonical OpenStack Messaging
by Rich Bowen
I received the following feedback from a user. Not sure if Daniel is on
this list to answer followup questions, but I'll encourage him to join.
--Rich
-------- Original Message --------
Date: Tue, 25 Feb 2014 12:39:01 +0800
From: Daniel Veillard <veillard(a)redhat.com>
BTW I installed RDO from scratch on a CentOS 6.5 box 2 weeks ago,
The Good:
1/ the instruction worked, no tweaking, packstack did work
even with the horrible connection I'm having at the moment
2/ the setup instructions are clear and simple
http://openstack.redhat.com/Quickstart
however it should be made clear that the host where the
installation is done should have a fully qualified DNS name
as that's one of the small issue I hit, and people doing testing
are likely to do it on machines without that set up
3/ I got the console working just fine
The Less Good:
Creating a CentOS test instance should be no more than an
additional 2 steps, it wasn't
http://openstack.redhat.com/Running_an_instance
Step 1 if CONTROL_NODE is not the IP (previous document referenced
an iP) then one need to pass a FQDN, in my case
http://test/dashboard fails with
"Openstack dashboard Something went wrong an unexpected error
has occured ..."
http://test.veillard.com/dashboard works
http://http://192.168.0.12/dashboard works
So either make sure the FQDN is part of the requirement in step 0
or like for the quickstart use $YOURIP that will also be coherent
=> I wonder how many get stuck at that step thinking their
installation is broken
Step 2 and 3 just fine
Step 4:
that's another issue, the default is a Fedora image, and that
worked fine but for CentOS i had to
- click the image resource link
- then follow CentOS 6.5 images
one end up at
http://repos.fedorapeople.org/repos/openstack/guest-images/
a CentOs image, one month old, hosted on Fedora, with no checksum
no README, etc ...
I do think that
http://openstack.redhat.com/Image_resources
need to be updated to point to a real web page, on the CentOS project
with a current image and followup instruction dedicated to people
who were following the RDO instructions
In comparison the http://cloud-images.ubuntu.com/ link for
"Ubuntu cloud images" at least has some pointers, we can do way
better and streamline for an RDO setup
Step 5:
Launch the instance instruction failed for me, just providing a
name was not sufficient, the error was
"At least one network must be specified."
it got me to the Networking tab and i had to pick the private
network from the available networks only selection, then launch
worked
Step 6:
it looks like it worked and got a 172.24.4.127 IP, but the instance
still says "IP address 10.0.0.3" , and trying in step 7 to ssh
to 172.24.4.127 failed, both from the remote workstation and
when logged as root
Then messed up creating a local pool of IPs as suggested at
http://openstack.redhat.com/Floating_IP_range
but tuned to the local IP address, registering the network was fine
but it never seems used when trying to associate a floating IP to
the instance.
=> IMHO we need to fix quite a few things so that instructions work
out of the box up to running and ssh'ing to a CentOS instance.
Rich, are you able to sort and fix those points at least up to
networking setup ?
KB, do we have a page with QCow2 ready CentOS image on the centos site
that we could link to, and provide RDO tuned instructions ?
Daniel
10 years, 1 month
[Rdo-list] [OFI] Dynflow orchestration POC draft
by Petr Chalupa
Hello,
I'm sending out a Dynflow orchestration draft for proof-of-concept to
start a discussion.
With regards to having it asap I would use:
1. [Dynflow][1] - workflow engine written originally for Katello.
2. [ForemanTasks][2] - Rails engine that adds Dynflow integration with
Foreman.
3. [Astapor manifests][3] - top level classes configuring OpenStack HA
hosts. There is [top-level puppet class][4] for each role.
4. [Puppetrun][5] - to manually trigger puppet run on Foreman host.
## Minimal POC
Minimal POC would be reusing Astapor manifests. There would be dynflow
added to avoid the manual steps between configuring OpenStack hosts
(Controllers then Computes, etc.).
It would start by triggering Dynflow action which would:
1. provision needed number of hosts in parallel.
2. configure all-in-on controller using Astapor class.
- adding the class to the host.
- triggering puppet run.
3. configure nova compute hosts using Astapor class. Same sub-steps.
4. configure additional hosts in right order with neutron, swift, cinder.
(I'll probably start with µ-POC skipping 1. and 4.)
## Open questions
- Is there a simpler way how to trigger puppet run on a given host?
- From a quick look Astapor modules should work for us, needs to be
verified.
- What would you improve?
- Do you see any compilations?
[1]: https://github.com/Dynflow/dynflow/
[2]: https://github.com/inecas/foreman-tasks
[3]:
https://github.com/redhat-openstack/astapor/tree/master/puppet/modules/qu...
[4]:
https://github.com/redhat-openstack/astapor/blob/master/bin/seeds.rb#L323...
[5]: http://projects.theforeman.org/projects/foreman/wiki/Puppetrun
I'll also send another email describing better solution to support
multiple layouts later this week.
Petr
10 years, 1 month
