Re: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

[joehuang]

Hi, Shinobu, 

You found a bug, yeah. The design has been moved to the master branch, so the 
description:

'Note: Stateless proposal is working on the “experiment” branch:'
'https://github.com/openstack/tricircle/tree/experiment'

Just been removed from the design blueprint as you mentioned.

Best Regards
Chaoyi Huang ( Joe Huang )


-Original Message-
From: Shinobu Kinjo [mailto:shinobu...@gmail.com] 
Sent: Saturday, May 14, 2016 2:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

Hi Team,

In page1, we define "stateless design" as follows:

Note: Stateless proposal is working on the “experiment” branch:
https://github.com/openstack/tricircle/tree/experiment

But, in section 7, we define this design as follows:

A PoC was done to verify the feasibility of stateless architecture.
Since the feedback of this PoC was very positive, sorce codes of the stateless 
design was moved to the master branch of the Tricircle git repository

Since that, I am thinking of deleting former description (definition in page1).

Make sense?

Cheers,
Shinobu

--
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

[Shinobu Kinjo]

Hi Team,

Sorry for this spam -;
Please ignore previous message.

I will file that as a doc bug.

Cheers,
S


On Sat, May 14, 2016 at 3:36 PM, Shinobu Kinjo  wrote:
> Hi Team,
>
> In page1, we define "stateless design" as follows:
>
> Note: Stateless proposal is working on the “experiment” branch:
> https://github.com/openstack/tricircle/tree/experiment
>
> But, in section 7, we define this design as follows:
>
> A PoC was done to verify the feasibility of stateless architecture.
> Since the feedback of this PoC was very positive, sorce codes of the
> stateless design was moved to the master branch of the Tricircle git
> repository
>
> Since that, I am thinking of deleting former description (definition in 
> page1).
>
> Make sense?
>
> Cheers,
> Shinobu
>
> --
> Email:
> shin...@linux.com
> shin...@redhat.com



-- 
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tricircle] [Blueprint] Stateless design definition

[Shinobu Kinjo]

Hi Team,

In page1, we define "stateless design" as follows:

Note: Stateless proposal is working on the “experiment” branch:
https://github.com/openstack/tricircle/tree/experiment

But, in section 7, we define this design as follows:

A PoC was done to verify the feasibility of stateless architecture.
Since the feedback of this PoC was very positive, sorce codes of the
stateless design was moved to the master branch of the Tricircle git
repository

Since that, I am thinking of deleting former description (definition in page1).

Make sense?

Cheers,
Shinobu

-- 
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev