Re: Roadmap for 4.x and 5.0

[ilya]

Marc

You are correct that my shell script is not most robust - it should  be
re-written in java - and called upon on "graceful" shutdown - this
script should be treated as POC i guess.

What it guards against - is more than just snapshots though. Basically -
any async operation that would be harmful to end user experience if i
was to take down one of the MS servers.

I front my MS servers with a VIP, as i take down one of the MS servers
gracefully via script below, the agents all reconnect to next MS.



The current "Cold Cross Cluster" migration as it stands is done by
copying the data disk to secondary and then back to primary. If you have
a VMs with 4TB data disks - thats not feasible for several reasons (1
NFS export for SSVM may not be as large, its pretty slow to copy to NFS
and back to Primary - even if you have a robust network). Hence direct
migration bypassing the secondary store would be far more efficient.

In regards to secure KVM migration, each migrate call, establishes a
one-time SSH key pair between 2 KVM host that will be used only for the
duration of that migration. It is cleared once the operation completes
and avoids a possibility of someone exploiting the cloud user ssh keys.

This is not a big deal to Cloud Hosting companies - but is a big deal to
enterprise security folks who run cloudstack as private cloud. We don't
want cloud user keys littered everywhere - not very ideal in terms of
security.

Regards
ilya



On 7/3/16 10:41 PM, ma...@exoscale.ch wrote:
> Hi Ilya,
> 
> Regarding the live migration, we are using it in production and did migrate a 
> couple of VMs until we reach some corner cases, for which I wrote a few 
> fixes. We'll verify them during the following weeks. The code is based on CS 
> 4.4 but I started porting it to master. I have to finish that and merge the 
> fixes too. For the cold migration, it's already in CS and we are usign it 
> since a while.
> What do you mean by secure KVM migration? My code reads configuration values 
> for which you can have TLS peer-2-peer connection between the agents to 
> transfert over it all the data using the features in libvirt. That the setup 
> we have in production.
> 
> For the graceful shutdown, we have a HA proxy in front so we just edit the 
> configuration to turn off one MS. We are also checking manually if there 
> aren't any snapshot ongoing before launching the stop-start. But I don't find 
> this very robust. Therefore I read a lot of the code managing the agent and 
> how the agents are connected to the MS. There is already a command to 
> rebalance agents between MS, so I'm developping a solution around that.
> 
> Kind regards,
> Marc-Aurèle
> 
> 
>> On 02 Jul 2016, at 02:03, ilya  wrote:
>>
>> Marco,
>>
>> I written a tiny shell script that does following:
>>
>> Make's sure there are async_jobs that arent running, also block 8080 via
>> iptables - to avoid user connecting to MS thats about to go down.
>>
>> It needs a bit of enhancement - and should lookup the MSID of that
>> specific server, it looks something like this - consider borrowing
>> concepts if applicable..
>>
>>> #!/bin/bash
>>> DATESTAMP=$(date +%m%d%y-%H%M%S)
>>> DBPASS=$(java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar 
>>> org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI input="$(cat 
>>> /etc/cloudstack/management/db.properties | grep db.cloud.password | awk 
>>> -F'(' '{print $2}' | sed 's/)//g')" password="$(cat 
>>> /etc/cloudstack/management/key)" | grep -A2 OUTPUT | tail -1)
>>> DBHOST=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.host 
>>> | awk -F'=' '{print $2}' | tail -1 )
>>> DBUSER=$(cat /etc/cloudstack/management/db.properties | grep 
>>> db.cloud.username | awk -F'=' '{print $2}')
>>> DB=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.name | 
>>> awk -F'=' '{print $2}')
>>> DBPORT=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.port 
>>> | awk -F'=' '{print $2}')
>>> MYSQLCMD="mysql -h $DBHOST -u $DBUSER -P $DBPORT -p$DBPASS $DB"
>>> #echo $DBPASS $DBHOST $DBUSER $DB $DBPORT
>>>
>>>
>>> JOBS=$(echo 'SELECT * FROM cloud.async_job where job_status=0 and 
>>> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD | wc -l)
>>>
>>> if [ $JOBS -gt 0 ]
>>>then
>>>echo "WARN: Looks like i have active jobs in flight, please 
>>> try again later"
>>>echo 'SELECT * FROM cloud.async_job where job_status=0 and 
>>> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD
>>>exit
>>>else
>>>echo "NOTE: No jobs running, good to go!"
>>>echo "NOTE: Blocking incoming 8080"
>>>/sbin/iptables -A INPUT -p tcp --destination-port 8080 -j 
>>> DROP
>>>service cloudstack-management stop
>>>service cloudstack-management stop:wq
>>>CSPID=$(cat /var/run/cloudstack-management.pid )
>>>

Re: Roadmap for 4.x and 5.0

[ma...@exoscale.ch]

Hi Ilya,

Regarding the live migration, we are using it in production and did migrate a 
couple of VMs until we reach some corner cases, for which I wrote a few fixes. 
We'll verify them during the following weeks. The code is based on CS 4.4 but I 
started porting it to master. I have to finish that and merge the fixes too. 
For the cold migration, it's already in CS and we are usign it since a while.
What do you mean by secure KVM migration? My code reads configuration values 
for which you can have TLS peer-2-peer connection between the agents to 
transfert over it all the data using the features in libvirt. That the setup we 
have in production.

For the graceful shutdown, we have a HA proxy in front so we just edit the 
configuration to turn off one MS. We are also checking manually if there aren't 
any snapshot ongoing before launching the stop-start. But I don't find this 
very robust. Therefore I read a lot of the code managing the agent and how the 
agents are connected to the MS. There is already a command to rebalance agents 
between MS, so I'm developping a solution around that.

Kind regards,
Marc-Aurèle


> On 02 Jul 2016, at 02:03, ilya  wrote:
> 
> Marco,
> 
> I written a tiny shell script that does following:
> 
> Make's sure there are async_jobs that arent running, also block 8080 via
> iptables - to avoid user connecting to MS thats about to go down.
> 
> It needs a bit of enhancement - and should lookup the MSID of that
> specific server, it looks something like this - consider borrowing
> concepts if applicable..
> 
>> #!/bin/bash
>> DATESTAMP=$(date +%m%d%y-%H%M%S)
>> DBPASS=$(java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar 
>> org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI input="$(cat 
>> /etc/cloudstack/management/db.properties | grep db.cloud.password | awk 
>> -F'(' '{print $2}' | sed 's/)//g')" password="$(cat 
>> /etc/cloudstack/management/key)" | grep -A2 OUTPUT | tail -1)
>> DBHOST=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.host | 
>> awk -F'=' '{print $2}' | tail -1 )
>> DBUSER=$(cat /etc/cloudstack/management/db.properties | grep 
>> db.cloud.username | awk -F'=' '{print $2}')
>> DB=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.name | awk 
>> -F'=' '{print $2}')
>> DBPORT=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.port | 
>> awk -F'=' '{print $2}')
>> MYSQLCMD="mysql -h $DBHOST -u $DBUSER -P $DBPORT -p$DBPASS $DB"
>> #echo $DBPASS $DBHOST $DBUSER $DB $DBPORT
>> 
>> 
>> JOBS=$(echo 'SELECT * FROM cloud.async_job where job_status=0 and 
>> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD | wc -l)
>> 
>> if [ $JOBS -gt 0 ]
>>then
>>echo "WARN: Looks like i have active jobs in flight, please 
>> try again later"
>>echo 'SELECT * FROM cloud.async_job where job_status=0 and 
>> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD
>>exit
>>else
>>echo "NOTE: No jobs running, good to go!"
>>echo "NOTE: Blocking incoming 8080"
>>/sbin/iptables -A INPUT -p tcp --destination-port 8080 -j DROP
>>service cloudstack-management stop
>>service cloudstack-management stop:wq
>>CSPID=$(cat /var/run/cloudstack-management.pid )
>>ps -p $CSPID >/dev/null 2>&1 && (kill -9 $CSPID)
>>ps -p $CSPID >/dev/null 2>&1 && (echo "ERROR: Count not 
>> terminame cloudstack service on `hostname` with pid $SCPID"; /sbin/iptables 
>> -D INPUT -p tcp --destination-port 8080 -j DROP; exit 1)
>>service cloudstack-management start
>>echo "NOTE: Unblocking incoming 8080"
>>/sbin/iptables -D INPUT -p tcp --destination-port 8080 -j DROP
>> fi
> 
> Regards,
> ilya
> 
> On 7/1/16 3:30 AM, ma...@exoscale.ch wrote:
>> Hi,
>> 
>> I can't edit the page but I'll be glad to put some effort for the V5:
>> - Live migration for KVM
>> - Improve logging using UUIDs (as I already did part of that for us at 
>> exoscale)
>> 
>> I'm in the process to add another feature we need: graceful shutdown of a 
>> management server when running a cluster of MS. The goal is to send a 
>> "prepareForShutdown" command to one or more MS and have them rebalance their 
>> agents to the ones still running so that no command will be lost. Then there 
>> shouldn't be any downtime with any agent during an update.
>> 
>> Kind regards,
>> Marc-Aurèle
>> 
>> PS: Is there any architectural discussion going on on the Slack channel? I 
>> saw that the IRC is not so active...
>> 
>> 
>>> On 01 Jul 2016, at 11:55, Paul Angus  wrote:
>>> 
>>> There's not been much response to this, but I'll start clearing away the 
>>> unclaimed items, people can always add them back.
>>> 
>>> 
>>> Kind regards,
>>> 
>>> Paul Angus
>>> 
>>> 
>>> paul.an...@shapeblue.com 
>>> www.shapeblue.com

Re: Roadmap for 4.x and 5.0

[ilya]

Marco,

I written a tiny shell script that does following:

Make's sure there are async_jobs that arent running, also block 8080 via
iptables - to avoid user connecting to MS thats about to go down.

It needs a bit of enhancement - and should lookup the MSID of that
specific server, it looks something like this - consider borrowing
concepts if applicable..

> #!/bin/bash
> DATESTAMP=$(date +%m%d%y-%H%M%S)
> DBPASS=$(java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar 
> org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI input="$(cat 
> /etc/cloudstack/management/db.properties | grep db.cloud.password | awk -F'(' 
> '{print $2}' | sed 's/)//g')" password="$(cat 
> /etc/cloudstack/management/key)" | grep -A2 OUTPUT | tail -1)
> DBHOST=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.host | 
> awk -F'=' '{print $2}' | tail -1 )
> DBUSER=$(cat /etc/cloudstack/management/db.properties | grep 
> db.cloud.username | awk -F'=' '{print $2}')
> DB=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.name | awk 
> -F'=' '{print $2}')
> DBPORT=$(cat /etc/cloudstack/management/db.properties | grep db.cloud.port | 
> awk -F'=' '{print $2}')
> MYSQLCMD="mysql -h $DBHOST -u $DBUSER -P $DBPORT -p$DBPASS $DB"
> #echo $DBPASS $DBHOST $DBUSER $DB $DBPORT
> 
> 
> JOBS=$(echo 'SELECT * FROM cloud.async_job where job_status=0 and 
> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD | wc -l)
> 
> if [ $JOBS -gt 0 ]
> then
> echo "WARN: Looks like i have active jobs in flight, please 
> try again later"
> echo 'SELECT * FROM cloud.async_job where job_status=0 and 
> job_dispatcher not like "pseudoJobDispatcher"' | $MYSQLCMD
> exit
> else
> echo "NOTE: No jobs running, good to go!"
> echo "NOTE: Blocking incoming 8080"
> /sbin/iptables -A INPUT -p tcp --destination-port 8080 -j DROP
> service cloudstack-management stop
> service cloudstack-management stop:wq
> CSPID=$(cat /var/run/cloudstack-management.pid )
> ps -p $CSPID >/dev/null 2>&1 && (kill -9 $CSPID)
> ps -p $CSPID >/dev/null 2>&1 && (echo "ERROR: Count not 
> terminame cloudstack service on `hostname` with pid $SCPID"; /sbin/iptables 
> -D INPUT -p tcp --destination-port 8080 -j DROP; exit 1)
> service cloudstack-management start
> echo "NOTE: Unblocking incoming 8080"
> /sbin/iptables -D INPUT -p tcp --destination-port 8080 -j DROP
> fi

Regards,
ilya

On 7/1/16 3:30 AM, ma...@exoscale.ch wrote:
> Hi,
> 
> I can't edit the page but I'll be glad to put some effort for the V5:
> - Live migration for KVM
> - Improve logging using UUIDs (as I already did part of that for us at 
> exoscale)
> 
> I'm in the process to add another feature we need: graceful shutdown of a 
> management server when running a cluster of MS. The goal is to send a 
> "prepareForShutdown" command to one or more MS and have them rebalance their 
> agents to the ones still running so that no command will be lost. Then there 
> shouldn't be any downtime with any agent during an update.
> 
> Kind regards,
> Marc-Aurèle
> 
> PS: Is there any architectural discussion going on on the Slack channel? I 
> saw that the IRC is not so active...
> 
> 
>> On 01 Jul 2016, at 11:55, Paul Angus  wrote:
>>
>> There's not been much response to this, but I'll start clearing away the 
>> unclaimed items, people can always add them back.
>>
>>
>> Kind regards,
>>
>> Paul Angus
>>
>>
>> paul.an...@shapeblue.com 
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>>
> 

Re: Roadmap for 4.x and 5.0

[ilya]

Marco

RE:
> - Live migration for KVM

How far are you from completing this?

Reason i'm asking:

We have this feature completed as plugin for cross cluster migration for
LIVE VMs.
We would like to take it out of plugin and contribute it to cloudstack
core.
Also considering adding COLD VM cross cluster migration for KVM (which
should be much faster than LIVE).

We also would like to contribute the "secure" KVM migration feature.

Marcus has list of other things he has developed as plugins - that we
need to work on - contributing back to cloudstack.

Regards
ilya

On 7/1/16 6:26 AM, Paul Angus wrote:
> That sounds great. I'll get it added.
> 
> 
> Kind regards,
> 
> Paul Angus
> 
> paul.an...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: ma...@exoscale.ch [mailto:ma...@exoscale.ch] 
> Sent: 01 July 2016 11:31
> To: dev@cloudstack.apache.org
> Subject: Re: Roadmap for 4.x and 5.0
> 
> Hi,
> 
> I can't edit the page but I'll be glad to put some effort for the V5:
> - Live migration for KVM
> - Improve logging using UUIDs (as I already did part of that for us at 
> exoscale)
> 
> I'm in the process to add another feature we need: graceful shutdown of a 
> management server when running a cluster of MS. The goal is to send a 
> "prepareForShutdown" command to one or more MS and have them rebalance their 
> agents to the ones still running so that no command will be lost. Then there 
> shouldn't be any downtime with any agent during an update.
> 
> Kind regards,
> Marc-Aurèle
> 
> PS: Is there any architectural discussion going on on the Slack channel? I 
> saw that the IRC is not so active...
> 
> 
>> On 01 Jul 2016, at 11:55, Paul Angus <paul.an...@shapeblue.com> wrote:
>>
>> There's not been much response to this, but I'll start clearing away the 
>> unclaimed items, people can always add them back.
>>
>>
>> Kind regards,
>>
>> Paul Angus
>>
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>>
>>
>>
> 

RE: Roadmap for 4.x and 5.0

[Paul Angus]

That sounds great. I'll get it added.


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: ma...@exoscale.ch [mailto:ma...@exoscale.ch] 
Sent: 01 July 2016 11:31
To: dev@cloudstack.apache.org
Subject: Re: Roadmap for 4.x and 5.0

Hi,

I can't edit the page but I'll be glad to put some effort for the V5:
- Live migration for KVM
- Improve logging using UUIDs (as I already did part of that for us at exoscale)

I'm in the process to add another feature we need: graceful shutdown of a 
management server when running a cluster of MS. The goal is to send a 
"prepareForShutdown" command to one or more MS and have them rebalance their 
agents to the ones still running so that no command will be lost. Then there 
shouldn't be any downtime with any agent during an update.

Kind regards,
Marc-Aurèle

PS: Is there any architectural discussion going on on the Slack channel? I saw 
that the IRC is not so active...


> On 01 Jul 2016, at 11:55, Paul Angus <paul.an...@shapeblue.com> wrote:
> 
> There's not been much response to this, but I'll start clearing away the 
> unclaimed items, people can always add them back.
> 
> 
> Kind regards,
> 
> Paul Angus
> 
> 
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> 
> 
> 

Re: Roadmap for 4.x and 5.0

[ma...@exoscale.ch]

Hi,

I can't edit the page but I'll be glad to put some effort for the V5:
- Live migration for KVM
- Improve logging using UUIDs (as I already did part of that for us at exoscale)

I'm in the process to add another feature we need: graceful shutdown of a 
management server when running a cluster of MS. The goal is to send a 
"prepareForShutdown" command to one or more MS and have them rebalance their 
agents to the ones still running so that no command will be lost. Then there 
shouldn't be any downtime with any agent during an update.

Kind regards,
Marc-Aurèle

PS: Is there any architectural discussion going on on the Slack channel? I saw 
that the IRC is not so active...


> On 01 Jul 2016, at 11:55, Paul Angus  wrote:
> 
> There's not been much response to this, but I'll start clearing away the 
> unclaimed items, people can always add them back.
> 
> 
> Kind regards,
> 
> Paul Angus
> 
> 
> paul.an...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> 
> 

RE: Roadmap for 4.x and 5.0

[Paul Angus]

There's not been much response to this, but I'll start clearing away the 
unclaimed items, people can always add them back.


Kind regards,

Paul Angus


paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Roadmap for 4.x and 5.0

[Tutkowski, Mike]

I just added my name and Syed Ahmed's name for "Snapshots on SAN".

Thanks,
Mike

From: Paul Angus <paul.an...@shapeblue.com>
Sent: Saturday, June 18, 2016 12:15 PM
To: dev@cloudstack.apache.org; rwhee...@artifact-software.com
Subject: RE: Roadmap for 4.x and 5.0

I brought up the subject of updating this page a month or so ago.  To try and 
get some movement, here is a list of all of the titles with nobody's name 
against them:



If no one claims them then I’ll remove them at the end of next week….



Packaging:

YAML based configs



Logging/Metrics:

Use MDC

Improve logging using UUIDs and internal metrics

Better error handling

Processing Logs



Storage :

Remove NFS dependency

Snapshots on SAN

Network

Improved GSLB

Network ACLS

Globo DNS API

VR: dnsmasq to better dns

Better LB

Improve VR, VR agent, API for VR

Hybrid setups across domains

L2 on L3 (sbp)

VPC: inter vpc, private gateways

GSLB Multi-zone



UI, API:

2Factor Authentication

Refactor API + core



Misc:

Disaster Recovery, Import infra

Terraform support

Architecture

Refactor management Core

Apparmour/Selinux support (KVM)

Persistance layer: away from DAO

Architecture changes/upgrade





Kind regards,



Paul Angus



paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: 17 June 2016 15:25
To: dev@cloudstack.apache.org
Subject: Roadmap for 4.x and 5.0





https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap



Needs updating. Some of the work must have been completed since it is slotted 
for 4.6.



Perhaps this is the page to start laying out the "new" release protocol and to 
start to collect the tasks for 4.10 and 4.11



It would also be a good place to collect ideas for 5.0 so that we can see what 
the proposed release numbering and delivery schedule actually means in terms of 
delivery of functionality.



The mailing list discussion has been pretty robust and a lot of writing has 
been done that deserves a more permanent home and some more concrete 
descriptions of proposed work.



Ron



--

Ron Wheeler

President

Artifact Software Inc

email: rwhee...@artifact-software.com<mailto:rwhee...@artifact-software.com>

skype: ronaldmwheeler

phone: 866-970-2435, ext 102

Re: Roadmap for 4.x and 5.0

[Ron Wheeler]

I added 2 columns to 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap to 
facilitate the discussion.


"Last Updated" can give the reader some idea about the currency of the 
information.
"Comments" should allow some light discussion. Heavy discussion could be 
a good indication that the item needs its own child page.


Please have a look to see if any of these tasks are yours and bring them 
up to date.
If you think that a task has died, please at least add a comment or if 
you are certain, delete the task.


Feel free to remove my questions from the comment field if you update 
the task status.


The title of the page is Roadmap and it starts out "This is the roadmap 
for CloudStack code development." which implies that there is some level 
of shared commitment to implement these things within a timeframe that 
would match users expectations for "soon".


A lot of the items do not have JIRAs.
Does this mean that they are so far out in the future that they are not 
really relevant to a roadmap and should be moved to a "wishlist"?


The title also gives the expectation that this covers all of the major 
enhancements in the foreseeable future.

Anything that is being worked on for 4.10 should be on this list by now.

Ron


On 17/06/2016 10:25 AM, Ron Wheeler wrote:


https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap

Needs updating. Some of the work must have been completed since it is 
slotted for 4.6.


Perhaps this is the page to start laying out the "new" release 
protocol and to start to collect the tasks for 4.10 and 4.11


It would also be a good place to collect ideas for 5.0 so that we can 
see what the proposed release numbering and delivery schedule actually 
means in terms of delivery of functionality.


The mailing list discussion has been pretty robust and a lot of 
writing has been done that deserves a more permanent home and some 
more concrete descriptions of proposed work.


Ron




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

RE: Roadmap for 4.x and 5.0

[Paul Angus]

I brought up the subject of updating this page a month or so ago.  To try and 
get some movement, here is a list of all of the titles with nobody's name 
against them:



If no one claims them then I’ll remove them at the end of next week….



Packaging:

YAML based configs



Logging/Metrics:

Use MDC

Improve logging using UUIDs and internal metrics

Better error handling

Processing Logs



Storage :

Remove NFS dependency

Snapshots on SAN

Network

Improved GSLB

Network ACLS

Globo DNS API

VR: dnsmasq to better dns

Better LB

Improve VR, VR agent, API for VR

Hybrid setups across domains

L2 on L3 (sbp)

VPC: inter vpc, private gateways

GSLB Multi-zone



UI, API:

2Factor Authentication

Refactor API + core



Misc:

Disaster Recovery, Import infra

Terraform support

Architecture

Refactor management Core

Apparmour/Selinux support (KVM)

Persistance layer: away from DAO

Architecture changes/upgrade





Kind regards,



Paul Angus



paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: 17 June 2016 15:25
To: dev@cloudstack.apache.org
Subject: Roadmap for 4.x and 5.0





https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap



Needs updating. Some of the work must have been completed since it is slotted 
for 4.6.



Perhaps this is the page to start laying out the "new" release protocol and to 
start to collect the tasks for 4.10 and 4.11



It would also be a good place to collect ideas for 5.0 so that we can see what 
the proposed release numbering and delivery schedule actually means in terms of 
delivery of functionality.



The mailing list discussion has been pretty robust and a lot of writing has 
been done that deserves a more permanent home and some more concrete 
descriptions of proposed work.



Ron



--

Ron Wheeler

President

Artifact Software Inc

email: rwhee...@artifact-software.com

skype: ronaldmwheeler

phone: 866-970-2435, ext 102