In regards to your last comment, that "it would be great for tenants
to be able to setup connections into AWS", HP CSA comes close to doing
that:
http://www8.hp.com/us/en/software-solutions/cloud-service-automation/
It's not *exactly* what you're looking for, you wouldn't be using the
OpenStack
On Mon, Oct 3, 2016 at 11:52 AM, Jonathan Proulx wrote:
>
> So my sense from responses so far:
>
> No one is doing unified SDN solutions across clouds and no one really
> wants to.
I do want to (but am not doing). When I worked at a public cloud based
on openstack we
Hello,
Kolla deprecates Heka in Ocata cycle, because Mozilla doesn't support
this project any more. During Ocata cycle we will prepare migration
plan and alternative to fill this missing functionality. As part of
N->O cycle we will migrate Heka to alternative we will decide upon in
following
Definitely read (and re-read) the release notes here:
https://wiki.openstack.org/wiki/ReleaseNotes/Liberty
paying close attention to the Upgrade Notes, API changes, etc.
You might also search (google or otherwise) this distribution list for
history on this topic as many of us did this q
On
Definitely read (and re-read) the release notes here:
https://wiki.openstack.org/wiki/ReleaseNotes/Liberty
paying close attention to the Upgrade Notes, API changes, etc.
You might also search (google or otherwise) this distribution list for
history on this topic as many of us did this quite
Hi all,
Can anybody please share your experience with upgrading a Kilo environment to
Liberty? More specifically I have a Kilo environment deployed and managed under
Fuel 7.0, and I am looking for a path to upgrade it to Liberty. I would
certainly like to:
- Keep it under management
Excerpts from Jonathan Proulx's message of 2016-10-03 13:52:42 -0400:
>
> So my sense from responses so far:
>
> No one is doing unified SDN solutions across clouds and no one really
> wants to.
>
> Consensus is just treat each network island like another remote DC and
> use normal VPN type
So my sense from responses so far:
No one is doing unified SDN solutions across clouds and no one really
wants to.
Consensus is just treat each network island like another remote DC and
use normal VPN type stuff to glue them together.
( nod to http://romana.io an interesting looking network
I think the best general way to view networking in cloud is WAN vs Cloud
Lan.
There's almost always an edge routing env for your cloud environments (
whether they be by region or by policy or by tim is an angry dude and you
don't touch his instances ).
Everything beyond that edge is a WAN
This can also be done with IPv4 address as well. Not quite the flexibility
that comes with v6, but workable for all but the very largest environments.
This is the approach that is embodied in the Romana (http://romana.io/) project
(I am part of this effort).
If you run all your OpenStack VMs on
Excerpts from Jonathan Proulx's message of 2016-10-03 11:16:03 -0400:
> On Sat, Oct 01, 2016 at 02:39:38PM -0700, Clint Byrum wrote:
>
> :I know it's hard to believe, but this world was foretold long ago and
> :what you want requires no special equipment or changes to OpenStack,
> :just
On Sat, Oct 01, 2016 at 02:39:38PM -0700, Clint Byrum wrote:
:I know it's hard to believe, but this world was foretold long ago and
:what you want requires no special equipment or changes to OpenStack,
:just will-power. You can achieve it now if you can use operating system
:versions published
Hi Ops Meetups Team,
Friday, a few of us met to discuss the current version of the agenda [1]. We
made a few tweaks and have a few items to discuss at the next meeting. Namely:
- We removed the scheduled session for lightning talks because room for them is
in the Ops war stories track
- We
Sorry I missed the Mailing List in the Cc:
Saverio
2016-10-03 9:15 GMT+02:00 Saverio Proto :
> Hello Kevin,
>
> thanks for your answer.
>
> so far I managed to make the network not shared just by making it not
> external. Because I dont need NAT and floatingips this will match
Hello Matt,
first of all in the file : plugins/ml2/openvswitch_agent.ini
you need to have bridge mappings, in my case for example:
bridge_mappings = physnet1:br-eth3,physnet2:br-eth4
this will define what physnet1 means in the openstack context. To
create the external network I do:
openstack
15 matches
Mail list logo