>
> On Sep 8, 2016, at 3:11 PM, Sean Dague wrote:
>
> On 09/08/2016 09:04 AM, Andrew Laski wrote:
>>
>>
>> On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote:
>>> On 09/07/2016 07:34 PM, Andrew Laski wrote:
On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> On Thu,
On 09/08/2016 09:04 AM, Andrew Laski wrote:
>
>
> On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote:
>> On 09/07/2016 07:34 PM, Andrew Laski wrote:
>>>
>>>
>>> On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
3) core func
______________
> > From: Andrew Laski [and...@lascii.com]
> > Sent: Wednesday, September 07, 2016 4:34 PM
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance
> > with Floating IP
> >
> &
34 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch
> instance with Floating IP
>
> On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> > On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> &g
On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote:
> On 09/07/2016 07:34 PM, Andrew Laski wrote:
> >
> >
> > On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> >> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> >> 3) core functionality should IMO require as few API calls as
f...
>> > openstack standard library api api? (yes, double apis) Where you
>> > can build up an api using other api calls and users can rely on
>> > those standard overarching api's to be there?
>> >
>> > Thanks,
>> > Kevin
>> > _
On 09/07/2016 07:34 PM, Andrew Laski wrote:
>
>
> On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
>> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
>> 3) core functionality should IMO require as few API calls as possible,
>> to as few components as possible, while keeping REST
rarching api's to be there?
> >
> > Thanks,
> > Kevin
> >
> > From: Andrew Laski [and...@lascii.com]
> > Sent: Wednesday, September 07, 2016 4:34 PM
> > To: openstack-dev@lists.openstack.org
> > Subject: R
ls and users can rely on those standard overarching api's
> to be there?
>
> Thanks,
> Kevin
>
> From: Andrew Laski [and...@lascii.com]
> Sent: Wednesday, September 07, 2016 4:34 PM
> To: openstack-dev@lists.openstack.org
> Sub
Kevin
From: Andrew Laski [and...@lascii.com]
Sent: Wednesday, September 07, 2016 4:34 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with
Floating IP
On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> On Thu, 2016-09-
> From: Adrian Turjak [adri...@catalyst.net.nz]
> > Sent: Wednesday, September 07, 2016 2:34 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch
> > instance with Floating IP
&g
On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> > This is exactly what something like Minstral would be fantastic for.
> > Multi-project workflow.
> > Rather than try and build logic like this directly into nova, looks
> > at ex
On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote:
> This is exactly what something like Minstral would be fantastic for.
> Multi-project workflow.
> Rather than try and build logic like this directly into nova, looks
> at extending something like Minstral with a basic easy to call task.
I ha
ailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP
>
> This is exactly what something like Minstral would be fantastic for. Multi-project workflow.
>
> Rather than try and build logic like this directly into
t for usage questions)
Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with
Floating IP
This is exactly what something like Minstral would be fantastic for.
Multi-project workflow.
Rather than try and build logic like this directly into nova, looks at
extending some
This is exactly what something like Minstral would be fantastic for. Multi-project workflow.
Rather than try and build logic like this directly into nova, looks at extending something like Minstral with a basic easy to call task.
_
p's also could also solve.
Thanks,
Kevin
From: Monty Taylor [mord...@inaugust.com]
Sent: Wednesday, September 07, 2016 10:00 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with
Floating I
__
> From: Monty Taylor [mord...@inaugust.com]
> Sent: Wednesday, September 07, 2016 8:55 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance
> with Floating IP
>
> On 09/07/2016 03:31 AM, Martin
7, 2016 8:55 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with
Floating IP
On 09/07/2016 03:31 AM, Martin Millnert wrote:
> Hi Matt,
>
> On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
>> Floating IP
On 09/07/2016 03:31 AM, Martin Millnert wrote:
> Hi Matt,
>
> On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
>> Floating IPs aren't required in OpenStack deployments, and anyone
>> running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
>> or
>> support them, at least with
On Wed, Sep 7, 2016, at 04:31 AM, Martin Millnert wrote:
> Hi Matt,
>
> On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
> > Floating IPs aren't required in OpenStack deployments, and anyone
> > running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
> > or
> > support the
Hi Matt,
On Tue, 2016-09-06 at 16:39 -0500, Matt Riedemann wrote:
> Floating IPs aren't required in OpenStack deployments, and anyone
> running with cells v1 (Rackspace, GoDaddy, NeCTAR, CERN) doesn't use
> or
> support them, at least without patching Nova. So I'm not sure what
> 'industry stan
On 9/6/2016 2:48 PM, Martin Millnert wrote:
Hi,
Goal:
I'd like to replicate the industry standard of providing a on-by-
default (UI) option to auto-assign a floating IP to a newly launched
instance. It must be toggleable however (to follow industry standard).
Floating IPs aren't required in
23 matches
Mail list logo
