+1 for both! Congrats :)
On Nov 25, 2014, at 12:16 PM, Nikhil Komawar
nikhil.koma...@rackspace.commailto:nikhil.koma...@rackspace.com wrote:
Hi all,
Please consider this email as a nomination for Erno and Alex (CC) for adding
them to the list of Glance core reviewers. Over the last cycle,
+1
On Sep 15, 2014, at 9:37 AM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
I would like to propose Radoslav to be a core team member. Over the course of
the J cycle he has been great with the reviews, bug fixes and updates to the
project.
Can the other core team
+1, That’s what suggested in the blueprint a year ago:
https://blueprints.launchpad.net/glance/+spec/transfer-rate-limiting
It looks like consensus during summit discussion that rate limiting should be
a separate facility running as a proxy in front of glance.”
Thanks,
Arnaud
On Aug 8, 2014,
+1
On Jul 30, 2014, at 2:19 PM, Chris Behrens
cbehr...@codestud.commailto:cbehr...@codestud.com wrote:
+1
On Jul 30, 2014, at 2:02 PM, Michael Still
mi...@stillhq.commailto:mi...@stillhq.com wrote:
Greetings,
I would like to nominate Jay Pipes for the nova-core team.
Jay has been involved
Hi Malini,
I would be pleased to work with you on the effort to make the import of OVA
working out of tree using the Glance tasks.
I am sure many people will be delighted by this feature and I also agree with
Mark in the fact that there might be a problem a message by bringing this
feature in
Hi Denis,
I think this is a perfect time for you to review the spec for the glance
metadata catalog https://review.openstack.org/#/c/98554/ and see if it fits
your use case.
Also, we have a session tomorrow at 9:00am PST at the Glance meetup to discuss
this topic. I think it would be useful if
Greetings,
A couple of updates for the meetup tomorrow:
- The schedule of the meetup can be found here:
https://wiki.openstack.org/wiki/Glance/JunoCycleMeetup
- We will start at 9:00 AM PST:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140725T09p1=1240
- It will be possible to
The spec to allow Nova to support Glance v1 and v2 got an exception for the
Juno Spec Freeze: see [1].
The spec has been created in April and went through 16 iterations.
The spec has been discussed several times already especially at the last Glance
meetup in Washington D.C.
A couple of
Greetings,
I am facing an issue and looking for guidance/best practice. So, here is the
problem:
- glance [stable/icehouse] contains a requirement to oslo.vmware = 0.2 [1] and
consequently requirements/global-requirements [stable/icehouse] also contains
oslo.vmware = 0.2.[2] So far nothing
Hi All,
Glance is going to have bug days next week on July Tuesday 15 and Wednesday 16.
This is a two-days bug day to accommodate most of the Glance contributors (time
zones, etc.). Of course, You do not need to be 100% two days…
This is a great opportunity to:
- triage bugs
- fix bugs
- tag
@ZhiYan: I don't like the idea of removing the sample configuration file(s)
from the git repository. Many people do not want to have to checkout the entire
codebase and tox every time they have to verify a variable name in a
configuration file. I know many people who were really frustrated
To: Arnaud Legendre alegen...@vmware.com
Cc: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, June 17, 2014 8:43:38 AM
Subject: Re: [openstack-dev] [glance] Unifying configuration file
On Tue, Jun 17 2014, Arnaud Legendre wrote:
@ZhiYan: I
+1 Good job Nikhil!
- Original Message -
From: Brian Rosmaita brian.rosma...@rackspace.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, June 12, 2014 10:15:07 AM
Subject: Re: [openstack-dev] [Glance] Nominating
Hi Folks
We are currently working on the logistic to organize the Glance mid-cycle
meetup.
What we know so far:
- it will happen in California, USA (either in Palo Alto or San Francisco),
- it will be a 3 days event in the week Jul 28th - Aug 1st (either Monday to
Wednesday or Tuesday to
Greetings!
The glance-specs repository is now opened!
- If you have a blueprint that is targeted for Juno-1 and Approved: you do not
need to create a spec. Only two blueprints seem to fall into this category. See
[1] for more details.
- If you have a blueprint in Launchpad (approved or not,
Hi Matt,
I totally agree with you and actually we have been discussing this a lot
internally the last few weeks.
. As a top priority, the driver MUST integrate with oslo.vmware. This will be
achieved through this chain of patches [1]. We want these patches to be merged
before other things.
I
Hi Alexander, Thank you for your input.
I think we need to clearly define what a version means for an artifact.
First, I would like to comeback to the definition of an artifact: this broader
audience might not be aware of this concept.
As of today, my understanding is the following:
An
Hi Qui Xing,
We are planning to address the vCenter template issue by levering the OVF/OVA
capabilities.
Kiran's implementation is tied to a specific VC and requires to add Glance
properties that are not generic.
For existing templates, the workflow will be:
. generate an *.ova tarball
18 matches
Mail list logo
