On 11/25/2014 05:33 PM, Angelo Matarazzo wrote:
>
> Hi all,
> my team and I are working on pxe boot feature very similar to the
> "Discless VM" one in Active blueprint list[1]
> The blueprint [2] is no longer active and we created a new spec [3][4].
>
> Nova core reviewers commented our spec and
- Original Message -
> From: "Angelo Matarazzo"
> To: "OpenStack Development Mailing" ,
> openstack-operat...@lists.openstack.org
>
>
> Hi all,
> my team and I are working on pxe boot feature very similar to the
> "Discless VM" one in Active blueprint list[1]
> The blueprint [2] is no
The use case we were thinking about is a Network Function (e.g. IMS
Nodes) implementation in which the high availability is based on
OpenSAF. In this scenario there is an Active/Standby cluster of 2 System
Controllers (SC) plus several Payloads (PL) that boot from network,
controlled by the SC.
On Wed, Dec 3, 2014 at 1:16 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> The use case we were thinking about is a Network Function (e.g. IMS Nodes)
> implementation in which the high availability is based on OpenSAF. In this
> scenario there is an Active/Standby cluster of 2 Sy
Well, one of the main reason to choose an open source product is to
avoid vendor lock-in. I think it is not
advisableto embed in the software running in an instance a call to
OpenStack specific services.
On 12/10/14 00:20, Joe Gordon wrote:
On Wed, Dec 3, 2014 at 1:16 AM, Pasquale Porreca
On Wed, Dec 10, 2014 at 7:42 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Well, one of the main reason to choose an open source product is to avoid
> vendor lock-in. I think it is not
> advisable to embed in the software running in an instance a call to
> OpenStack specific se
- Original Message -
> From: "Pasquale Porreca"
> To: openstack-dev@lists.openstack.org
>
> Well, one of the main reason to choose an open source product is to
> avoid vendor lock-in. I think it is not
>
> advisable to embed in the software running in an instance a call to
> OpenStack sp
>From my point of view it is not advisable to base some functionalities
of the instances on direct calls to Openstack API. This for 2 main
reasons, the first one: if the Openstack code changes (and we know
Openstack code does change) it will be required to change the code of
the software running in
It is possible to decide in advance how many PL will be necessary for a
service, so their creation can be decided externally from the SC. Anyway
the role that any PL should assume and so the image to install on each
PL should be decided by the SC.
On 12/12/14 09:54, Steve Gordon wrote:
> - Ori
On Fri, Dec 12, 2014 at 1:48 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> From my point of view it is not advisable to base some functionalities
> of the instances on direct calls to Openstack API. This for 2 main
> reasons, the first one: if the Openstack code changes (and we
10 matches
Mail list logo