Please propose a new network documentation page as part of this discussion.
If it makes it more palatable to developers, we could rename the
documentation to "Use Cases".
That would make it easier to discuss the real impact on users of what is
being proposed.
The current network documentation is one of the biggest barriers to
entry and generates a lot of the traffic in the forum.
Ron
On 06/07/2018 4:50 AM, Paul Angus wrote:
Sorry for being late to the party.
'in theory' couldn't we do away with the idea that 'advanced networking with
security groups' is a type of zone and just allow the use of security groups in
any network, instead of making people 'choose' up front.
I believe AWS allows the use of security groups in VPCs. It seems a little
'belt and braces', but I know of users who have looked to do it.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-----Original Message-----
From: Wido den Hollander <w...@widodh.nl>
Sent: 19 June 2018 21:58
To: dev@cloudstack.apache.org
Subject: [DISCUSS] Blocking the creation of new Basic Networking zones
Hi,
We (PCextreme) are a big-time user of Basic Networking and recently started to
look into Advanced Networking with VLAN isolation and a shared network.
This provides (from what we can see) all the features Basic Networking
provides, like the VR just doing DHCP and UserData while the Hypervisor does
the Security Grouping.
That made me wonder why we still have Basic Networking.
Dropping all the code would be a big problem for users as you can't simply
migrate from Basic to Advanced. In theory we found out that it's possible by
changing the database, but I wouldn't guarantee it works in every use-case. So
doing this automatically during a upgrade would be difficult.
To prevent us from having to maintain the Basic Networking code for ever I
would like to propose and discuss the matter of preventing the creation of new
Basic Networking zones.
In the future this can get us rid of a lot of if-else statements in the code
and it would make testing also easier as we have few things to test.
Most of the development also seems to go in the Advanced Networking direction.
We are currently also working on IPv6 in Advanced Shared Networks and that's
progressing very good as well.
Would this be something to call the 5.0 release where we simplify the
networking and in the UI/API get rid of Basic Networking while keeping it alive
for existing users?
Wido
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
