Is there any chance of having horizon distribution in its current
state (i.e., with openstack_dashboard and other 3rd-party stuff) on
PyPi? Because the 'next' milestone assigned to this blueprint suggests
(at least to me) that the separation is not going to happen soon :).
On Thu, Mar 13, 2014 at
I can chair this one, no worries.
I have the below topics in mind :
- no-db scheduler blueprint
- scheduler forklift efforts
- open discussion
Any other subjects to discuss ?
-Sylvain
Le 17 mars 2014 00:55, "Dugger, Donald D" a
écrit :
>
>
> I can't make the meeting this week so, unless someon
Hi Boris,
I just read the other thread. As Jay asked in [1], have you considered
precautions in the UI in stead? That should take care of mistakes with manual
deletes.
Thx
Subbu
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-March/029784.html
On Mar 16, 2014, at 10:37 PM, Boris P
Hi Stackers,
Currently we are working on supporting import existing ESXi/distributed port
groups into Neutron under Cluster level(which vmware nova driver managed
level). By doing it, nova could be able to deploy vm to multiple port groups
without NSX plugin. Now the called vmware agent is fo
Hi Stackers,
Currently we are working on supporting import existing ESXi/distributed port
groups into Neutron under Cluster level(which vmware nova driver managed
level). By doing it, nova could be able to deploy vm to multiple port groups
without NSX plugin. Now the called vmware agent is fo
Subbu,
No it's not too late. It's just proposal for Juno.
First of all, you should keep in mind that in you cause it's probably
automated. In case of Web Hosting it's done by end users (so it's not
automated).
If you spend some time and read discussion about removing "Soft deletion"
[1] you'll s
Hope this is not too late to ask this question, but isn't this extra code just
fat finger mistakes?
IME, most provisioning on cloud happens via automated tools, and it seems
counter-productive to design a feature for manual operations.
Thx,
Subbu
On Mar 13, 2014, at 12:42 PM, Boris Pavlovic w
On Mon, Mar 17, 2014 at 3:21 PM, Christopher Yeoh wrote:
> To accommodate those who happen to find the blueprint first, I think we
> need a link from the blueprint to the nova-specs review or when its
> approved into the nova-specs repository. I kind of expected the link
> from the blueprint to r
On Mon, 17 Mar 2014 13:58:20 +1100
Michael Still wrote:
> So I've written a blueprint for nova for Juno, and uploaded it to
> nova-specs (https://review.openstack.org/#/c/80865/). That got me
> thinking about what this process might look like, and this is what I
> came up with:
>
> * create a lau
On Mon, Mar 17, 2014 at 3:00 PM, Chris Behrens wrote:
>
> On Mar 16, 2014, at 7:58 PM, Michael Still wrote:
>
>> Hi.
>>
>> So I've written a blueprint for nova for Juno, and uploaded it to
>> nova-specs (https://review.openstack.org/#/c/80865/). That got me
>> thinking about what this process mig
On Mar 16, 2014, at 7:58 PM, Michael Still wrote:
> Hi.
>
> So I've written a blueprint for nova for Juno, and uploaded it to
> nova-specs (https://review.openstack.org/#/c/80865/). That got me
> thinking about what this process might look like, and this is what I
> came up with:
>
> * create
Right now PBR's creation of versions for postversioning is problematic
- it generates versions that (if recognized by pip) would be treated
as releases, even when its a non-tagged commit.
https://etherpad.openstack.org/p/pbr-postversion-semver
The tl;dr is a proposal to generate dev marked versio
Hi.
So I've written a blueprint for nova for Juno, and uploaded it to
nova-specs (https://review.openstack.org/#/c/80865/). That got me
thinking about what this process might look like, and this is what I
came up with:
* create a launchpad blueprint
* you write a proposal in the nova-specs repo
*
Hi, Oscar
First, openstack-qa ML is deprecated now as I said before. So please do
not send an e-mail to openstack-qa ML.
On 03/10, Oscar Correia wrote:
> I have new test case and I would like add inside Tempest directory and
> after execute, example: test case Swift for object and container. How
All,
Many times we've heard a desire for more feedback and interaction from
users. However, their attendance at design summit sessions is met with
varied success.
However, last summit, by happy accident, a swift session turned into a
something a lot more user driven. A competent user was abl
I can't make the meeting this week so, unless someone else wants to volunteer
to run the meeting, let's cancel this one.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lis
On 17 March 2014 10:32, Steve Baker wrote:
> On 17/03/14 10:14, Robert Collins wrote:
>> On 17 March 2014 09:20, Steve Baker wrote:
>>
>>> It looks like the cert files you want to transfer are all ascii rather than
>>> binary, which is good as we have yet to implement a way to attach binary
>>> d
On 17 March 2014 09:20, Steve Baker wrote:
> It looks like the cert files you want to transfer are all ascii rather than
> binary, which is good as we have yet to implement a way to attach binary
> data to a heat stack create call.
>
> One way to write out these files would be using cloud-config.
On 17/03/14 10:14, Robert Collins wrote:
> On 17 March 2014 09:20, Steve Baker wrote:
>
>> It looks like the cert files you want to transfer are all ascii rather than
>> binary, which is good as we have yet to implement a way to attach binary
>> data to a heat stack create call.
>>
>> One way to w
On 15/03/14 02:33, Jiří Stránský wrote:
> On 12.3.2014 17:03, Jiří Stránský wrote:
>>
>> Thanks for all the replies everyone :)
>>
>> I'm leaning towards going the way Robert suggested on the review [1] -
>> upload pre-created signing cert, signing key and CA cert to controller
>> nodes using Heat.
Interesting, the usage of stop to do this could work since the semantics are
similar enough. People could even remap delete to stop and force-delete to
delete and this would be a solution as well (or as u said use a
cronjob/deletion service/janitor crew that does the force-delete).
Good idea!
On Fri, 2014-03-14 at 13:43 -0700, Vishvananda Ishaya wrote:
> Awesome, this is exactly what I was thinking. I think this is really
> close to being usable on the nova side. First of all the
> dot.sperated.form looks better imo, and I think my code should still
> work that way as well. The other pi
Excerpts from Renat Akhmerov's message of 2014-03-13 01:55:46 -0700:
> Joshua,
>
> Thanks for your interest and feedback.
>
> I believe you were able to deliver your message already, we definitely hear
> you. So no need to the same stuff again and again ;) As I promised before, we
> are now eva
Hi all,
I'd like to extend port capability using ML2 binding:profile. I checked
the official docs and it seems that there's no guide for it.
Is there any CLI support for port binding:profile?
Or is there any development guide on how to set up "profile"?
--
---
cheers,
Li Ma
Excerpts from Adam Young's message of 2014-03-12 06:19:47 -0700:
> On 03/11/2014 01:20 PM, Clint Byrum wrote:
> > Excerpts from Adam Young's message of 2014-03-11 07:50:58 -0700:
> >> On 03/11/2014 05:25 AM, Dmitry Mescheryakov wrote:
> >>> For what it's worth in Sahara (former Savanna) we inject t
25 matches
Mail list logo
