Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Received-SPF: pass (athena.apache.org: domain of
 prvs=687783408e=ctooley2@express-scripts.com designates 167.211.4.32 as
 permitted sender)
From: "Tooley, Christopher Tooley (STL) - contr"
	<CTooley2@express-scripts.com>
To: "dev@deltacloud.apache.org" <dev@deltacloud.apache.org>
Subject: Networking Components for Deltacloud OpenStack Driver
Thread-Topic: Networking Components for Deltacloud OpenStack Driver
Thread-Index: Ac5pNGjfySVbU7fAT128mjs9YXWtRg==
Date: Fri, 14 Jun 2013 19:21:45 +0000
Message-ID: 
 <6073B8059A638640887EF4B786F8C7C3E0ED@HQ4P1W12796.accounts.root.corp>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_6073B8059A638640887EF4B786F8C7C3E0EDHQ4P1W12796accounts_"
MIME-Version: 1.0

--_000_6073B8059A638640887EF4B786F8C7C3E0EDHQ4P1W12796accounts_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Our ideal solution to our cloud platform has become to use Deltacloud to fr=
ont-end our virtualization platforms. One of those platforms we will be rel=
ying heavily on is OpenStack. I see that Deltacloud will make API calls to =
EC2 for Load Balancers, IP Addresses and Firewalls. All of those things see=
m to be supported in OpenStack's Quantum API so I was hoping to avoid writi=
ng directly to OpenStack when Deltacloud supports it.

Is there any work being done to move that forward? If so, where? If not, an=
y pointers on where to start would help.

It appears that Deltacloud traffic is really dropping off based on the numb=
er of messages per month to the mailing list. Am I looking at the wrong lis=
t, catching the community at a bad time, or is the project losing that much=
 in terms of people's available time?

I'm hoping that soon I'll be able to contribute if that is seen as a valuab=
le thing.

Chris Tooley


--_000_6073B8059A638640887EF4B786F8C7C3E0EDHQ4P1W12796accounts_--