[Openstack] Nova and Glance Grizzly RC2 available !

2013-03-30 Thread Thierry Carrez
Hello everyone,

Here is the last round of this week's respins. Due to various reported
bugs (including an issue upgrading from Nova Folsom to Grizzly), we
created new Grizzly release candidates for OpenStack Compute (Nova)
and OpenStack Image Service (Glance).

You can find those RC2 tarballs and see lists of fixed bugs at:
https://launchpad.net/nova/grizzly/grizzly-rc2
https://launchpad.net/glance/grizzly/grizzly-rc2

These are hopefully the last Grizzly release candidates for Nova and
Glance. Unless new release-critical regressions are found that warrant a
last-minute release candidate respin, those RC2s will be formally
included in the common OpenStack 2013.1 final release next week. You are
therefore strongly encouraged to test and validate those tarballs.

Alternatively, you can grab the code at:
https://github.com/openstack/nova/tree/milestone-proposed
https://github.com/openstack/glance/tree/milestone-proposed

If you find a regression that could be considered release-critical,
please file it on Launchpad and tag it *grizzly-rc-potential* to bring
it to the release crew's attention.

Release day is Thursday !

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OpenStack Grizzly Install Guide

2013-03-30 Thread Shake Chen
Thanks for your great guide. I would test it next week.


On Fri, Mar 29, 2013 at 6:13 PM, skible openstack 
skible.openst...@gmail.com wrote:

 Hi Stackers,

 I present to you my new guide : OpenStack Grizzly Install Guide by Bilel
 Msekni. https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide

 This is an easy way to deploy Grizzly on a single node and get to know the
 new features it presents ! Two branches are currently created :

 1- (master) Quantum + linuxbridge
 2- (OVS_SingleNode) Quantum + OVS

 More guides will be published soon to cover multinode deployment.

 I hope you enjoy this work and please don't hesitate to give me your
 feedbacks.

 Let's make of OpenStack a Success :)

 Kind regards,
 Bilel Msekni

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
Shake Chen
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Announcing Climate, OpenStack Capacity Leasing project

2013-03-30 Thread Sean Roberts
Interested. Will post. Cheer!

~sean

On Mar 25, 2013, at 9:49 AM, Julien Danjou jul...@danjou.info wrote:

 Hi there,
 
 I'd like to announce a new project named Climate.
 
 The project
 aims to provide a capacity leasing service inside OpenStack
 cloud platforms,
 via the reservation of various resources in a calendar
 based view.
 
 The
 project is still as its early draft stage, but anyone with ideas
 and
 interest is welcome!
 
 Homepage:
 https://launchpad.net/climate
 
 Cheers,
 --
 Julien Danjou
 ;; Free Software
 hacker ; freelance consultant
 ;; http://julien.danjou.info
 
 
 ATT1.bin
 ATT2.txt

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [PATCH] Unify services and hosts API

2013-03-30 Thread Alessio Ababilov
Hi, Dan!

Could you have a look at my patch
https://review.openstack.org/#/c/18577/and possibly change your
-2,please?

-- 
Alessio Ababilov
Senior Software Engineer
Grid Dynamics
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [PATCH] Unify services and hosts API

2013-03-30 Thread Dan Smith
 Could you have a look at my patch
 https://review.openstack.org/#/c/18577/and possibly change your
 -2,please?

I don't think the patch has changed to address my concerns. If I'm
wrong, lets discuss it in the review comments so the other interested
reviewers can weigh in.

Thanks!

-- 
Dan Smith
IBM Linux Technology Center



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Forcing a VM to a specific node in grizzly

2013-03-30 Thread Lorin Hochstein
I see that in grizzly an admin can use a scheduler hint to force a VM to
launch on a particular host, e.g.:

nova boot --image 1 --flavor 2 --key_name test --hint force_hosts=server2
my-first-server
(from:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html
)

In Folsom, an admin could do this with the availability zone flag:

nova boot --image uuid --flavor m1.tiny --key_name test
--availability-zone nova:server2

(from:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-zone-to-boot-instances-on.html
)

Does the second method work in grizzly as well? If so, should we recommend
one approach over the other in the docs?

Lorin
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Forcing a VM to a specific node in grizzly

2013-03-30 Thread Vishvananda Ishaya
I wasn't aware that force_hosts actually works. Someone should probably verify. 
The availability zone method still works in grizzly.

Vish

On Mar 30, 2013, at 6:42 PM, Lorin Hochstein lo...@nimbisservices.com wrote:

 I see that in grizzly an admin can use a scheduler hint to force a VM to 
 launch on a particular host, e.g.:
 
 nova boot --image 1 --flavor 2 --key_name test --hint force_hosts=server2 
 my-first-server
 (from: 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html)
 
 In Folsom, an admin could do this with the availability zone flag:
 
 nova boot --image uuid --flavor m1.tiny --key_name test --availability-zone 
 nova:server2
 
 (from: 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-zone-to-boot-instances-on.html)
 
 Does the second method work in grizzly as well? If so, should we recommend 
 one approach over the other in the docs? 
 
 Lorin
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_nova_trunk #863

2013-03-30 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/863/Project:precise_grizzly_nova_trunkDate of build:Sat, 30 Mar 2013 02:31:34 -0400Build duration:2 hr 36 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesSync in matchmaker and qpid Conf changes from osloby jogoeditnova/openstack/common/rpc/impl_qpid.pyeditnova/openstack/common/rpc/matchmaker.pyquantum security group driver nova list shows same groupby aroseneditnova/tests/api/openstack/compute/contrib/test_quantum_security_groups.pyeditnova/tests/api/openstack/compute/contrib/test_security_groups.pyeditnova/api/openstack/compute/contrib/security_groups.pyConsole Output[...truncated 9188 lines...]Host Architecture: amd64Install-Time: 68Job: nova_2013.1+git201303300232~precise-0ubuntu1.dscMachine Architecture: amd64Package: novaPackage-Time: 9265Source-Version: 1:2013.1+git201303300232~precise-0ubuntu1Space: 120448Status: attemptedVersion: 1:2013.1+git201303300232~precise-0ubuntu1Finished at 20130330-0508Build needed 02:34:25, 120448k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'nova_2013.1+git201303300232~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'nova_2013.1+git201303300232~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/grizzly /tmp/tmpBXo4MO/novamk-build-deps -i -r -t apt-get -y /tmp/tmpBXo4MO/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 73f580449dd68a9bbfe4455788b62bf49210d348..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.1+git201303300232~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [c76ee40] quantum security group driver nova list shows same groupdch -a [50bd3e5] Sync in matchmaker and qpid Conf changes from oslodch -a [f7d8952] 'injected_files' should be base 64 encoded.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201303300232~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201303300232~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'nova_2013.1+git201303300232~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'nova_2013.1+git201303300232~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp