[GitHub] cloudstack pull request: CLOUDSTACK-8394: Skip test cases through ...

[gauravaradhye]

GitHub user gauravaradhye opened a pull request:

https://github.com/apache/cloudstack/pull/203

CLOUDSTACK-8394: Skip test cases through setUp() instead of setUpClass()

When the tests are skipped through setUpClass, the statement "raise 
unittest.SkipTest()" is used. This is seen as exception in the logs. To avoid 
this, alternatively we can set class level variable in setUpClass and read this 
variable value in setUp() and skip the test case.

All test cases are run and tested.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gauravaradhye/cloudstack 8394

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/203.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #203


commit cc52d395727be657c9b96a8c9dca10f3b051ee70
Author: Gaurav Aradhye 
Date:   2015-04-28T06:55:23Z

CLOUDSTACK-8394: Skip test cases through setUp() instead of setUpClass()




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8394: Skip test cases through ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/203


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-singlerun #1154

[jenkins]

See 

Re: [4.6] Trouble with virtual router

[Mike Tutkowski]

Huh...it doesn't work on KVM either (this is on Ubuntu 14.04). The failure
is a bit different, though. In this case, the SSVM stays in the Running
state, but the agent doesn't seem to ever come up.

Oh well...I guess I'll try ESXi later.

On Mon, Apr 27, 2015 at 11:45 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Thanks for the message, Abhi.
>
> I went ahead and deleted the host tag from each of my XenServer hosts
> (it's a new environment, so I only had one host tag per host). I then
> performed a force reconnect on each host.
>
> Unfortunately, I still seem to be encountering the same issue (even after
> destroying and re-creating the VR). This seems broken on both XenServer 6.2
> and XenServer 6.1.
>
> I think I will give it a try with ESXi 5.1 or KVM. I'm mainly interested
> in dealing with XenServer (for the time being) for this particular feature
> I'm working on, but perhaps I can at least get the system VMs up and
> running on another hypervisor to allow me to move forward.
>
> On Mon, Apr 27, 2015 at 11:23 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> Had similar problem where SSVM and CPVM came up but not the VR.
>> In my case I traced it to systemvm.iso not getting updated on XenServer,
>> due to the old host-tag.
>> On deleting the host tag the MS was able to copy the systemvm.iso to Xen
>> and things were fine after that.
>>
>> -abhi
>>
>>
>> > On 28-Apr-2015, at 10:15 am, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>> >
>> > Hi,
>> >
>> > Tonight I tried to re-create a cloud from scratch and made use of the
>> > following system template:
>> >
>> >
>> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
>> >
>> > My SSVM and CPVM get IP addresses and seem to behave OK; however, my VR
>> > never gets into the Running state. It gets to a point and then is
>> restarted
>> > (this happens a couple times). Eventually CS gives up on it.
>> >
>> > I only have two XenServer 6.2 hosts in this environment. The system VMs
>> are
>> > running on local storage.
>> >
>> > Thoughts on this?
>> >
>> > Thanks!
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the cloud
>> > *™*
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

CFP Committee (Lead) for Seattle

[Daan Hoogland]

For the cloudstack day in Seattle in August we are looking for
volunteers to handle call-for-papers and talk-selection. Anyone out
there willing to help out for this day:
http://events.linuxfoundation.org/events/cloudstack-seattle

please volunteer by replying to Karen and me.
thanks,
-- 
Daan

Re: [MERGE] Browser based template or volume upload

[Daan Hoogland]

Rajani et al,

Great effort. Apache jenkins doesn't merge the pull request cleanly so
maybe a more careful manual merge is required. please go ahead. Travis
is fine and of course always right;)

On Tue, Apr 28, 2015 at 8:20 AM, Rajani Karuturi  wrote:
> We worked on below proposal for Browser based template or volume upload.
> development effort from @bvbharat, Koushik Das and @karuturi
> UI help from @bfederle , Jessica Wang and @rags22489664
> testing effort from Deepthi Machiraju and @sailajamada
>
> We believe this feature is ready to merge. If you have any
> objections/suggestions/comments, please let us know before tomorrow.
>
> Proposal discussion: http://markmail.org/message/ne6ucmnfqhkddnhu
> FS and testplan:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39620237
> pull request: https://github.com/apache/cloudstack/pull/199
>
> Thanks,
>
> ~Rajani



-- 
Daan

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29221712
  
--- Diff: 
engine/storage/image/src/org/apache/cloudstack/storage/image/store/TemplateObject.java
 ---
@@ -28,7 +28,6 @@
 import 
org.apache.cloudstack.engine.subsystem.api.storage.DataObjectInStore;
 import org.apache.cloudstack.engine.subsystem.api.storage.DataStore;
 import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine;
-import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine.Event;
--- End diff --

Re-add import or use ObjectInDataStoreStateMachine.Event on line 168.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8423: [Xenserver] Improved the...

[anshul1886]

GitHub user anshul1886 opened a pull request:

https://github.com/apache/cloudstack/pull/204

CLOUDSTACK-8423: [Xenserver] Improved the performance for processing of 
ClusterVMMetaDataSync command

Current way of processing can  cause slowness in DB if there are huge 
number of VMs

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-8423

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/204.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #204


commit a3e6974a94fa2af921a1b25542a2f1b637eec05e
Author: Anshul Gangwar 
Date:   2015-04-28T08:07:56Z

CLOUDSTACK-8423: [Xenserver] Improved the performance for processing of 
ClusterVMMetaDataSync command
which can cause slowness in DB if there are huge number of VMs




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29222011
  
--- Diff: 
services/secondary-storage/server/src/org/apache/cloudstack/storage/resource/HttpUploadServerHandler.java
 ---
@@ -0,0 +1,295 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package org.apache.cloudstack.storage.resource;
+
+import static io.netty.buffer.Unpooled.copiedBuffer;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONNECTION;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONTENT_LENGTH;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONTENT_TYPE;
+
+import java.io.IOException;
+import java.net.URI;
+import java.util.List;
+import java.util.Map;
+import java.util.Map.Entry;
+
+import org.apache.cloudstack.storage.template.UploadEntity;
+import org.apache.cloudstack.utils.imagestore.ImageStoreUtil;
+import org.apache.commons.lang.StringUtils;
+import org.apache.log4j.Logger;
+
+import com.cloud.exception.InvalidParameterValueException;
+
+import io.netty.buffer.ByteBuf;
+import io.netty.channel.Channel;
+import io.netty.channel.ChannelFuture;
+import io.netty.channel.ChannelFutureListener;
+import io.netty.channel.ChannelHandlerContext;
+import io.netty.channel.SimpleChannelInboundHandler;
+import io.netty.handler.codec.http.DefaultFullHttpResponse;
+import io.netty.handler.codec.http.FullHttpResponse;
+import io.netty.handler.codec.http.HttpContent;
+import io.netty.handler.codec.http.HttpHeaders;
+import io.netty.handler.codec.http.HttpMethod;
+import io.netty.handler.codec.http.HttpObject;
+import io.netty.handler.codec.http.HttpRequest;
+import io.netty.handler.codec.http.HttpResponseStatus;
+import io.netty.handler.codec.http.HttpVersion;
+import io.netty.handler.codec.http.LastHttpContent;
+import io.netty.handler.codec.http.QueryStringDecoder;
+import io.netty.handler.codec.http.multipart.DefaultHttpDataFactory;
+import io.netty.handler.codec.http.multipart.DiskFileUpload;
+import io.netty.handler.codec.http.multipart.FileUpload;
+import io.netty.handler.codec.http.multipart.HttpDataFactory;
+import io.netty.handler.codec.http.multipart.HttpPostRequestDecoder;
+import 
io.netty.handler.codec.http.multipart.HttpPostRequestDecoder.ErrorDataDecoderException;
+import 
io.netty.handler.codec.http.multipart.HttpPostRequestDecoder.IncompatibleDataDecoderException;
+import io.netty.handler.codec.http.multipart.InterfaceHttpData;
+import 
io.netty.handler.codec.http.multipart.InterfaceHttpData.HttpDataType;
+import io.netty.util.CharsetUtil;
+
+public class HttpUploadServerHandler extends 
SimpleChannelInboundHandler {
+private static final Logger logger = 
Logger.getLogger(HttpUploadServerHandler.class.getName());
+
+private static final HttpDataFactory factory = new 
DefaultHttpDataFactory(true);
+
+private final StringBuilder responseContent = new StringBuilder();
+
+private HttpRequest request;
+
+private HttpPostRequestDecoder decoder;
+
+private NfsSecondaryStorageResource storageResource;
+
+private String uuid;
+
+private boolean requestProcessed = false;
+
+private static final String HEADER_SIGNATURE = "X-signature";
--- End diff --

These strings are used at ApiServer as well, can you refactor them and put 
them in utils (HttpUtils) so they can be used/maintained from one place?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r2911
  
--- Diff: systemvm/patches/debian/config/etc/init.d/cloud-early-config ---
@@ -1156,6 +1156,36 @@ setup_secstorage() {
   fi
   setup_apache2 $ETH2_IP
 
+  log_it "setting up apache2 for post upload of volume/template"
+  a2enmod proxy
+  a2enmod proxy_http
+  a2enmod headers
+
+  SSL_FILE="/etc/apache2/sites-available/default-ssl"
+  PATTERN="RewriteRule ^\/upload\/(.*)"
+  CORS_PATTERN="Header set Access-Control-Allow-Origin"
+  if [ -f $SSL_FILE ]; then
+if grep -q "$PATTERN" $SSL_FILE ; then
+  log_it "rewrite rules already exist in file $SSL_FILE"
+else
+log_it "adding rewrite rules to file: $SSL_FILE"
+sed -i -e "s/<\/VirtualHost>/RewriteEngine On \n&/" $SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteCond %{HTTPS} =on \n&/" 
$SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteCond %{REQUEST_METHOD} =POST 
\n&/" $SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteRule ^\/upload\/(.*) 
http:\/\/127.0.0.1:8210\/upload?uuid=\$1 [P,L] \n&/" $SSL_FILE
--- End diff --

looks like /upload will be available only for localhost? will this cause an 
issue?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29222349
  
--- Diff: ui/scripts/templates.js ---
@@ -97,17 +100,24 @@
 reorder: cloudStack.api.actions.sort('updateTemplate', 
'templates'),
 actions: {
 add: {
-label: 'label.action.register.template',
+label: 'Add',
 messages: {
 notification: function(args) {
-return 
'label.action.register.template';
+return 'Register Template from URL';
 }
 },
 createForm: {
-title: 'label.action.register.template',
+title: 'Register Template from URL',
--- End diff --

Revert to use labels instead of hardcoding values.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29222317
  
--- Diff: ui/scripts/storage.js ---
@@ -68,7 +68,7 @@
 actions: {
 // Add volume
 add: {
-label: 'label.add.volume',
+label: 'Add',
--- End diff --

can you revert to using label.* instead of hardcoding label values since it 
would break i18n?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29222391
  
--- Diff: ui/scripts/templates.js ---
@@ -906,7 +1229,7 @@
 }
 },
 isextractable: {
-label: 'label.extractable',
+label: 'label.extractable.lower',
--- End diff --

is there a label, or you wish to lowercase it?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/199#issuecomment-96971442
  
Overall looks good, I'm yet to test it. Can you share any test reports 
against latest master with this branch?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Question regarding VM snapshot restrictions

[Anshul Gangwar]

Hi Jan-Arve,

In which order have you tried adding vCPUs and NICs?
i.e. After creating VM snapshot or before creating snapshot.
And have you deleted VM snapshots before adding vCPUs and NICs?

Regards,
Anshul

On 24-Apr-2015, at 5:58 pm, Jan-Arve Nygård 
mailto:jan.arve.nyg...@gmail.com>> wrote:

Hi,

With 4.5 there are some restrictions applied to VMs that have VM snapshots.
According to CLOUDSTACK-7688
 VM snapshot stops
working when the following operations are performed on VM with VM snapshots:

1. Volumes of VM are migrated to other storage
2. Add and remove NIC to/from VM
3. Attach and Detach volume to VM
4. Scale up/down of VM(change service offering)
5. Volume snapshot which is not major use case in this scenario
6. Resize volume
7. Live migration of VM which involves storage migration

Does anyone have more technical details about why this is restricted?

I tried some quick tests with XenServer 6.5 and CS 4.5.1 and I was able to
both revert and take VM snapshots in CloudStack while adding vCPU and NICs
on the hypervisor.

Thanks,

-thinktwo

Jenkins build is still unstable: simulator-singlerun #1155

[jenkins]

See 

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29224805
  
--- Diff: 
services/secondary-storage/server/src/org/apache/cloudstack/storage/resource/HttpUploadServerHandler.java
 ---
@@ -0,0 +1,295 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package org.apache.cloudstack.storage.resource;
+
+import static io.netty.buffer.Unpooled.copiedBuffer;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONNECTION;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONTENT_LENGTH;
+import static io.netty.handler.codec.http.HttpHeaders.Names.CONTENT_TYPE;
+
+import java.io.IOException;
+import java.net.URI;
+import java.util.List;
+import java.util.Map;
+import java.util.Map.Entry;
+
+import org.apache.cloudstack.storage.template.UploadEntity;
+import org.apache.cloudstack.utils.imagestore.ImageStoreUtil;
+import org.apache.commons.lang.StringUtils;
+import org.apache.log4j.Logger;
+
+import com.cloud.exception.InvalidParameterValueException;
+
+import io.netty.buffer.ByteBuf;
+import io.netty.channel.Channel;
+import io.netty.channel.ChannelFuture;
+import io.netty.channel.ChannelFutureListener;
+import io.netty.channel.ChannelHandlerContext;
+import io.netty.channel.SimpleChannelInboundHandler;
+import io.netty.handler.codec.http.DefaultFullHttpResponse;
+import io.netty.handler.codec.http.FullHttpResponse;
+import io.netty.handler.codec.http.HttpContent;
+import io.netty.handler.codec.http.HttpHeaders;
+import io.netty.handler.codec.http.HttpMethod;
+import io.netty.handler.codec.http.HttpObject;
+import io.netty.handler.codec.http.HttpRequest;
+import io.netty.handler.codec.http.HttpResponseStatus;
+import io.netty.handler.codec.http.HttpVersion;
+import io.netty.handler.codec.http.LastHttpContent;
+import io.netty.handler.codec.http.QueryStringDecoder;
+import io.netty.handler.codec.http.multipart.DefaultHttpDataFactory;
+import io.netty.handler.codec.http.multipart.DiskFileUpload;
+import io.netty.handler.codec.http.multipart.FileUpload;
+import io.netty.handler.codec.http.multipart.HttpDataFactory;
+import io.netty.handler.codec.http.multipart.HttpPostRequestDecoder;
+import 
io.netty.handler.codec.http.multipart.HttpPostRequestDecoder.ErrorDataDecoderException;
+import 
io.netty.handler.codec.http.multipart.HttpPostRequestDecoder.IncompatibleDataDecoderException;
+import io.netty.handler.codec.http.multipart.InterfaceHttpData;
+import 
io.netty.handler.codec.http.multipart.InterfaceHttpData.HttpDataType;
+import io.netty.util.CharsetUtil;
+
+public class HttpUploadServerHandler extends 
SimpleChannelInboundHandler {
+private static final Logger logger = 
Logger.getLogger(HttpUploadServerHandler.class.getName());
+
+private static final HttpDataFactory factory = new 
DefaultHttpDataFactory(true);
+
+private final StringBuilder responseContent = new StringBuilder();
+
+private HttpRequest request;
+
+private HttpPostRequestDecoder decoder;
+
+private NfsSecondaryStorageResource storageResource;
+
+private String uuid;
+
+private boolean requestProcessed = false;
+
+private static final String HEADER_SIGNATURE = "X-signature";
--- End diff --

which strings are you referring to? X-signature is very specific to this 
feature


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29224874
  
--- Diff: 
engine/storage/image/src/org/apache/cloudstack/storage/image/store/TemplateObject.java
 ---
@@ -28,7 +28,6 @@
 import 
org.apache.cloudstack.engine.subsystem.api.storage.DataObjectInStore;
 import org.apache.cloudstack.engine.subsystem.api.storage.DataStore;
 import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine;
-import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine.Event;
--- End diff --

havent seen any compilation error. will check.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29224917
  
--- Diff: systemvm/patches/debian/config/etc/init.d/cloud-early-config ---
@@ -1156,6 +1156,36 @@ setup_secstorage() {
   fi
   setup_apache2 $ETH2_IP
 
+  log_it "setting up apache2 for post upload of volume/template"
+  a2enmod proxy
+  a2enmod proxy_http
+  a2enmod headers
+
+  SSL_FILE="/etc/apache2/sites-available/default-ssl"
+  PATTERN="RewriteRule ^\/upload\/(.*)"
+  CORS_PATTERN="Header set Access-Control-Allow-Origin"
+  if [ -f $SSL_FILE ]; then
+if grep -q "$PATTERN" $SSL_FILE ; then
+  log_it "rewrite rules already exist in file $SSL_FILE"
+else
+log_it "adding rewrite rules to file: $SSL_FILE"
+sed -i -e "s/<\/VirtualHost>/RewriteEngine On \n&/" $SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteCond %{HTTPS} =on \n&/" 
$SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteCond %{REQUEST_METHOD} =POST 
\n&/" $SSL_FILE
+sed -i -e "s/<\/VirtualHost>/RewriteRule ^\/upload\/(.*) 
http:\/\/127.0.0.1:8210\/upload?uuid=\$1 [P,L] \n&/" $SSL_FILE
--- End diff --

nope. the rewrite is to localhost


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

network start/end ip update.

[Jeronimo Garcia]

Hi list is it possible to modify the start/end ip of a running network?

I'm ok restarting the vms/sysvms bound to the network but i need to chanfe
the start and move it a couple of ips forward.

I see in the database there's a vlan.description table that has a format
such as:

10.0.0.1-10.0.0.200  and it seems tempting.

The update network api call doesn't support what i want to do at the mo.

Let me know and Thanks!!

midokura failing with host unknown

[Daan Hoogland]

Anybody at midokura still on this list? Can you please have a look at

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.3:process
(default) on project cloud-plugin-network-midonet: Error resolving
project artifact: Could not transfer artifact com.ceph:rados:pom:0.1.4
from/to mido-maven-public-releases
(http://cs-maven.midokura.com/releases): cs-maven.midokura.com for
project com.ceph:rados:jar:0.1.4: Unknown host cs-maven.midokura.com
-> [Help 1]

-- 
Daan

Re: Question regarding VM snapshot restrictions

[Jan-Arve Nygård]

Thanks Anshul,

I did a quick test with adding vCPU and NIC in XenCenter after creating a
snapshot through CloudStack. I also tried reverting the VM to the snapshots
afterwards with the vCPU and NIC still added, and it worked OK.

This made curious about what the background and details for this patch is.
If it's specific to any hypervisor/version and maybe is fixed in XenServer
6.5?

If you have some more details about why this was patched I could maybe help
about with testing this with XenServer 6.5.


-thinktwo

2015-04-28 10:32 GMT+02:00 Anshul Gangwar :

> Hi Jan-Arve,
>
> In which order have you tried adding vCPUs and NICs?
> i.e. After creating VM snapshot or before creating snapshot.
> And have you deleted VM snapshots before adding vCPUs and NICs?
>
> Regards,
> Anshul
>
> On 24-Apr-2015, at 5:58 pm, Jan-Arve Nygård  > wrote:
>
> Hi,
>
> With 4.5 there are some restrictions applied to VMs that have VM snapshots.
> According to CLOUDSTACK-7688
>  VM snapshot stops
> working when the following operations are performed on VM with VM
> snapshots:
>
> 1. Volumes of VM are migrated to other storage
> 2. Add and remove NIC to/from VM
> 3. Attach and Detach volume to VM
> 4. Scale up/down of VM(change service offering)
> 5. Volume snapshot which is not major use case in this scenario
> 6. Resize volume
> 7. Live migration of VM which involves storage migration
>
> Does anyone have more technical details about why this is restricted?
>
> I tried some quick tests with XenServer 6.5 and CS 4.5.1 and I was able to
> both revert and take VM snapshots in CloudStack while adding vCPU and NICs
> on the hypervisor.
>
> Thanks,
>
> -thinktwo
>
>

Re: Question regarding VM snapshot restrictions

[Anshul Gangwar]

These restrictions are not there due to Hypervisor limitations. These 
limitations are due to way this feature is implemented in CloudStack.
If we allow those operation then they may work fine but in long run they may 
lead to corruption of VM etc. So to avoid those situation these restrictions 
are added till we we figure out the better way.

Regards,
Anshul

On 28-Apr-2015, at 3:27 pm, Jan-Arve Nygård 
mailto:jan.arve.nyg...@gmail.com>> wrote:

Thanks Anshul,

I did a quick test with adding vCPU and NIC in XenCenter after creating a
snapshot through CloudStack. I also tried reverting the VM to the snapshots
afterwards with the vCPU and NIC still added, and it worked OK.

This made curious about what the background and details for this patch is.
If it's specific to any hypervisor/version and maybe is fixed in XenServer
6.5?

If you have some more details about why this was patched I could maybe help
about with testing this with XenServer 6.5.


-thinktwo

2015-04-28 10:32 GMT+02:00 Anshul Gangwar 
mailto:anshul.gang...@citrix.com>>:

Hi Jan-Arve,

In which order have you tried adding vCPUs and NICs?
i.e. After creating VM snapshot or before creating snapshot.
And have you deleted VM snapshots before adding vCPUs and NICs?

Regards,
Anshul

On 24-Apr-2015, at 5:58 pm, Jan-Arve Nygård 
mailto:jan.arve.nyg...@gmail.com>
> wrote:

Hi,

With 4.5 there are some restrictions applied to VMs that have VM snapshots.
According to CLOUDSTACK-7688
 VM snapshot stops
working when the following operations are performed on VM with VM
snapshots:

1. Volumes of VM are migrated to other storage
2. Add and remove NIC to/from VM
3. Attach and Detach volume to VM
4. Scale up/down of VM(change service offering)
5. Volume snapshot which is not major use case in this scenario
6. Resize volume
7. Live migration of VM which involves storage migration

Does anyone have more technical details about why this is restricted?

I tried some quick tests with XenServer 6.5 and CS 4.5.1 and I was able to
both revert and take VM snapshots in CloudStack while adding vCPU and NICs
on the hypervisor.

Thanks,

-thinktwo

Re: [4.6] Trouble with virtual router

[Sanjeev N]

One of the reasons for VR not to come up is, once CS creates VR on
hypervisor, it does a ping on VR's management interface for centain no.of
of times. If it does not receive any response then it will shut down the
VR.

So when VR is coming up check its console and see any network issues.

On Tue, Apr 28, 2015 at 12:39 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Huh...it doesn't work on KVM either (this is on Ubuntu 14.04). The failure
> is a bit different, though. In this case, the SSVM stays in the Running
> state, but the agent doesn't seem to ever come up.
>
> Oh well...I guess I'll try ESXi later.
>
> On Mon, Apr 27, 2015 at 11:45 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Thanks for the message, Abhi.
> >
> > I went ahead and deleted the host tag from each of my XenServer hosts
> > (it's a new environment, so I only had one host tag per host). I then
> > performed a force reconnect on each host.
> >
> > Unfortunately, I still seem to be encountering the same issue (even after
> > destroying and re-creating the VR). This seems broken on both XenServer
> 6.2
> > and XenServer 6.1.
> >
> > I think I will give it a try with ESXi 5.1 or KVM. I'm mainly interested
> > in dealing with XenServer (for the time being) for this particular
> feature
> > I'm working on, but perhaps I can at least get the system VMs up and
> > running on another hypervisor to allow me to move forward.
> >
> > On Mon, Apr 27, 2015 at 11:23 PM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >> Had similar problem where SSVM and CPVM came up but not the VR.
> >> In my case I traced it to systemvm.iso not getting updated on XenServer,
> >> due to the old host-tag.
> >> On deleting the host tag the MS was able to copy the systemvm.iso to Xen
> >> and things were fine after that.
> >>
> >> -abhi
> >>
> >>
> >> > On 28-Apr-2015, at 10:15 am, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >> >
> >> > Hi,
> >> >
> >> > Tonight I tried to re-create a cloud from scratch and made use of the
> >> > following system template:
> >> >
> >> >
> >>
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
> >> >
> >> > My SSVM and CPVM get IP addresses and seem to behave OK; however, my
> VR
> >> > never gets into the Running state. It gets to a point and then is
> >> restarted
> >> > (this happens a couple times). Eventually CS gives up on it.
> >> >
> >> > I only have two XenServer 6.2 hosts in this environment. The system
> VMs
> >> are
> >> > running on local storage.
> >> >
> >> > Thoughts on this?
> >> >
> >> > Thanks!
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkow...@solidfire.com
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the cloud
> >> > *™*
> >>
> >> Find out more about ShapeBlue and our range of CloudStack related
> services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework >
> >> CloudStack Consulting
> >> CloudStack Software Engineering<
> >> http://shapeblue.com/cloudstack-software-engineering/>
> >> CloudStack Infrastructure Support<
> >> http://shapeblue.com/cloudstack-infrastructure-support/>
> >> CloudStack Bootcamp Training Courses<
> >> http://shapeblue.com/cloudstack-training/>
> >>
> >> This email and any attachments to it may be confidential and are
> intended
> >> solely for the use of the individual to whom it is addressed. Any views
> or
> >> opinions expressed are solely those of the author and do not necessarily
> >> represent those of Shape Blue Ltd or related companies. If you are not
> the
> >> intended recipient of this email, you must neither take any action based
> >> upon its contents, nor copy or show it to anyone. Please contact the
> sender
> >> if you believe you have received this email in error. Shape Blue Ltd is
> a
> >> company incorporated in England & Wales. ShapeBlue Services India LLP
> is a
> >> company incorporated in India and is operated under license from Shape
> Blue
> >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
> >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> is
> >> a company registered by The Republic of South Africa and is traded under
> >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tu

Re: Question regarding VM snapshot restrictions

[Jan-Arve Nygård]

Thanks Anshul, just what i wanted to know :)

-thinktwo

2015-04-28 12:16 GMT+02:00 Anshul Gangwar :

> These restrictions are not there due to Hypervisor limitations. These
> limitations are due to way this feature is implemented in CloudStack.
> If we allow those operation then they may work fine but in long run they
> may lead to corruption of VM etc. So to avoid those situation these
> restrictions are added till we we figure out the better way.
>
> Regards,
> Anshul
>
> On 28-Apr-2015, at 3:27 pm, Jan-Arve Nygård  > wrote:
>
> Thanks Anshul,
>
> I did a quick test with adding vCPU and NIC in XenCenter after creating a
> snapshot through CloudStack. I also tried reverting the VM to the snapshots
> afterwards with the vCPU and NIC still added, and it worked OK.
>
> This made curious about what the background and details for this patch is.
> If it's specific to any hypervisor/version and maybe is fixed in XenServer
> 6.5?
>
> If you have some more details about why this was patched I could maybe help
> about with testing this with XenServer 6.5.
>
>
> -thinktwo
>
> 2015-04-28 10:32 GMT+02:00 Anshul Gangwar  >:
>
> Hi Jan-Arve,
>
> In which order have you tried adding vCPUs and NICs?
> i.e. After creating VM snapshot or before creating snapshot.
> And have you deleted VM snapshots before adding vCPUs and NICs?
>
> Regards,
> Anshul
>
> On 24-Apr-2015, at 5:58 pm, Jan-Arve Nygård  
> > wrote:
>
> Hi,
>
> With 4.5 there are some restrictions applied to VMs that have VM snapshots.
> According to CLOUDSTACK-7688
>  VM snapshot stops
> working when the following operations are performed on VM with VM
> snapshots:
>
> 1. Volumes of VM are migrated to other storage
> 2. Add and remove NIC to/from VM
> 3. Attach and Detach volume to VM
> 4. Scale up/down of VM(change service offering)
> 5. Volume snapshot which is not major use case in this scenario
> 6. Resize volume
> 7. Live migration of VM which involves storage migration
>
> Does anyone have more technical details about why this is restricted?
>
> I tried some quick tests with XenServer 6.5 and CS 4.5.1 and I was able to
> both revert and take VM snapshots in CloudStack while adding vCPU and NICs
> on the hypervisor.
>
> Thanks,
>
> -thinktwo
>
>
>
>

Marvin Error

[Ian Southam]

Hi,

Latest Marvin build has an error in it.  Has anyone already worked out the 
cause before I put work into it?  Common.py will not load because of an 
unresolved symbol in vcenter.py

Traceback (most recent call last):
  File "/cloudstack/cloudstack/test/integration/smoke/misc/test_deploy_vm.py", 
line 33, in 
from marvin.lib.common import get_zone, get_domain, get_template
  File 
"/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/common.py", line 
91, in 
from marvin.lib.vcenter import Vcenter
  File 
"/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/vcenter.py", line 
22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute ‘_create_unverified_context'

—
Grts!
Ian

Add vdisk to kvm guest vm but console fail

[Conta Serviço Email]

Hi, Dev Team

I play with cloudstack 4.4.2 + centos 6.5 kvm. It is ok that I deploy an
instance to kvm host, and the console is ok too.

When I directly add a vdisk via virsh command to this instance, it is ok and
the disk is recongnised but the console in CS UI is fail.

After I remove the vdisk via virsh command from this instance, the console
in CS UI is ok.

How to debug this issue ? Thanks.

My Env:

I attache disk:
virsh# attach-disk 2 /dev/iscsi-pool-sdb/volume01 vdc
Disk attached successfully

And then I open the console of this instance, but I got fail with notice:
"Server Internal Error"

catalina.out:

DEBUG [c.c.a.t.Request] (AgentManager-Handler-10:null) Seq
3-2832482690639331409: Processing:  { Ans: , MgmtId: 13557697424736, via:
3, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.","wait":0}}]
}
DEBUG [c.c.a.t.Request] (catalina-exec-19:null) Seq 3-2832482690639331409:
Received:  { Ans: , MgmtId: 13557697424736, via: 3, Ver: v1, Flags: 10, {
Answer } }
DEBUG [c.c.a.m.AgentManagerImpl] (catalina-exec-19:null) Details from
executing class com.cloud.agent.api.GetVncPortCommand: No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.
ERROR [c.c.s.ConsoleProxyServlet] (catalina-exec-19:null) Unexepected
exception in ConsoleProxyServlet
java.lang.ClassCastException: com.cloud.agent.api.Answer cannot be cast to
com.cloud.agent.api.GetVncPortAnswer

Is possible to develop a iscsi storage plugin to guest instances for  kvm
hypervisor ?


Best Regards,

[DISCUSS] name for google API interface

[Sebastien Goasguen]

Folks,

The GCE API wrapper that Ian, Darren and myself are working on giving to 
cloudstack has a name ‘gstack’ which is currently in use by:
http://linux.die.net/man/1/gstack

Bit silly to have use that name but blame it on me.

We originally called it gcloud, but then Google renamed it’s CLI gcloud and we 
had to switch.

For IP clearance we need to show best effort at using a name that is not in use.

Any thoughts on a new name ?

gceapi ?
gcestack ?

-sebastien

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[rags22489664]

Github user rags22489664 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29233530
  
--- Diff: ui/scripts/storage.js ---
@@ -68,7 +68,7 @@
 actions: {
 // Add volume
 add: {
-label: 'label.add.volume',
+label: 'Add',
--- End diff --

Sure, will create a separate pull request for it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[rags22489664]

Github user rags22489664 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29233545
  
--- Diff: ui/scripts/templates.js ---
@@ -97,17 +100,24 @@
 reorder: cloudStack.api.actions.sort('updateTemplate', 
'templates'),
 actions: {
 add: {
-label: 'label.action.register.template',
+label: 'Add',
 messages: {
 notification: function(args) {
-return 
'label.action.register.template';
+return 'Register Template from URL';
 }
 },
 createForm: {
-title: 'label.action.register.template',
+title: 'Register Template from URL',
--- End diff --

Sure, will create a separate pull request for it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[rags22489664]

Github user rags22489664 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29233570
  
--- Diff: ui/scripts/templates.js ---
@@ -906,7 +1229,7 @@
 }
 },
 isextractable: {
-label: 'label.extractable',
+label: 'label.extractable.lower',
--- End diff --

Will check if this is incorrect and create a separate pull request if 
required.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] name for google API interface

[Rohit Yadav]

> On 28-Apr-2015, at 12:56 pm, Sebastien Goasguen  wrote:
>
> Folks,
>
> The GCE API wrapper that Ian, Darren and myself are working on giving to 
> cloudstack has a name ‘gstack’ which is currently in use by:
> http://linux.die.net/man/1/gstack
>
> Bit silly to have use that name but blame it on me.
>
> We originally called it gcloud, but then Google renamed it’s CLI gcloud and 
> we had to switch.
>
> For IP clearance we need to show best effort at using a name that is not in 
> use.
>
> Any thoughts on a new name ?
>
> gceapi ?
> gcestack ?

Both sound alright. How about gcebridge, gbridge, gapinterface 
(G+API+Interface)?

>
> -sebastien

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Marvin Error

[Rohit Yadav]

Hi Ian,

Turns out this is an environment issue, the attribute maybe only available with 
ssl module of Python 2.7+ and not all 2.x ones. I’ve fixed it on master now.

> On 28-Apr-2015, at 12:29 pm, Ian Southam  wrote:
>
> Hi,
>
> Latest Marvin build has an error in it.  Has anyone already worked out the 
> cause before I put work into it?  Common.py will not load because of an 
> unresolved symbol in vcenter.py
>
> Traceback (most recent call last):
>  File "/cloudstack/cloudstack/test/integration/smoke/misc/test_deploy_vm.py", 
> line 33, in 
>from marvin.lib.common import get_zone, get_domain, get_template
>  File 
> "/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/common.py", 
> line 91, in 
>from marvin.lib.vcenter import Vcenter
>  File 
> "/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/vcenter.py", 
> line 22, in 
>ssl._create_default_https_context = ssl._create_unverified_context
> AttributeError: 'module' object has no attribute ‘_create_unverified_context'
>
> —
> Grts!
> Ian

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Jenkins build is still unstable: simulator-4.5-singlerun #221

[jenkins]

See 

Re: [DISCUSS] name for google API interface

[sebgoa]

On Apr 28, 2015, at 2:18 PM, Rohit Yadav  wrote:

> 
>> On 28-Apr-2015, at 12:56 pm, Sebastien Goasguen  wrote:
>> 
>> Folks,
>> 
>> The GCE API wrapper that Ian, Darren and myself are working on giving to 
>> cloudstack has a name ‘gstack’ which is currently in use by:
>> http://linux.die.net/man/1/gstack
>> 
>> Bit silly to have use that name but blame it on me.
>> 
>> We originally called it gcloud, but then Google renamed it’s CLI gcloud and 
>> we had to switch.
>> 
>> For IP clearance we need to show best effort at using a name that is not in 
>> use.
>> 
>> Any thoughts on a new name ?
>> 
>> gceapi ?
>> gcestack ?
> 
> Both sound alright. How about gcebridge, gbridge, gapinterface 
> (G+API+Interface)?
> 

I'd like to avoid using 'bridge' since we had confusion a while back about 
cloudbridge...

>> 
>> -sebastien
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Marvin Error

[Srikanteswararao Talluri]

Yeah, it is available post 2.7.9, Its my bad to use the private variable
from module. I¹ll see If I can fix that.

~Talluri

On 28/04/15 5:54 pm, "Rohit Yadav"  wrote:

>Hi Ian,
>
>Turns out this is an environment issue, the attribute maybe only
>available with ssl module of Python 2.7+ and not all 2.x ones. I¹ve fixed
>it on master now.
>
>> On 28-Apr-2015, at 12:29 pm, Ian Southam 
>>wrote:
>>
>> Hi,
>>
>> Latest Marvin build has an error in it.  Has anyone already worked out
>>the cause before I put work into it?  Common.py will not load because of
>>an unresolved symbol in vcenter.py
>>
>> Traceback (most recent call last):
>>  File 
>>"/cloudstack/cloudstack/test/integration/smoke/misc/test_deploy_vm.py",
>>line 33, in 
>>from marvin.lib.common import get_zone, get_domain, get_template
>>  File 
>>"/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/common.py",
>> line 91, in 
>>from marvin.lib.vcenter import Vcenter
>>  File 
>>"/cloudstack/test/venv/lib/python2.7/site-packages/marvin/lib/vcenter.py"
>>, line 22, in 
>>ssl._create_default_https_context = ssl._create_unverified_context
>> AttributeError: 'module' object has no attribute
>>Œ_create_unverified_context'
>>
>> ‹
>> Grts!
>> Ian
>
>Regards,
>Rohit Yadav
>Software Architect, ShapeBlue
>M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>Blog: bhaisaab.org | Twitter: @_bhaisaab
>
>
>
>Find out more about ShapeBlue and our range of CloudStack related services
>
>IaaS Cloud Design &
>Build87eUIbwdSEb9GowMC62K5dqF8JJUcxQiF5L1NLZSo-N04_9RnOkwYm8kXFzdJBkyFP1ZRkginY
>CvvshGkloa3krD506R2nElv-2c0QNC0H0MuliyqYNYTwnHOeVsNWMJgI-Zq48tRIXbEb946SFP
>0tm4e/http%3A%2F%2Fshapeblue.com%2Fiaas-cloud-design-and-build%2F%2F>
>CSForge ­ rapid IaaS deployment
>frameworkg9Xvm8oKaxbEcF10KSZa5Qa-eR36AkIHbKWQbQpU4CT0Da2NNj9_UFGyaEzIGvz2ykzBwWIHOk
>fyErFKKcw1PU1WAYAHKU5j9j-MqsYb48W8t0cK5dgE4_8AnTscnej0sLDV0o5t2aNRD8kJl1TG
>3Cbikpw0r/http%3A%2F%2Fshapeblue.com%2Fcsforge%2F>
>CloudStack 
>ConsultingtfK2HPzeX0M-rIxFdddAcYFLmFA3VDGpdZXEJ13dEmtuDf9mJCzBzjJzCCaROeadTC6yGB5Fr_
>yYkEd_MQTP8lg2t90pjLbZHgefXnzshsriEvalCvHC_H-G7b3STObJwFZIdmbPCAb-wgrJtrmi
>1vuo-BsqLy/http%3A%2F%2Fshapeblue.com%2Fcloudstack-consultancy%2F>
>CloudStack Software
>EngineeringIwCj04qfLBi9oLhB1xfabHvIvD8wVxRLlkUTgTXJMMhS-cfo8M5fxi1SCkJ0puiCUhCk-UwSgU
>cPD5l7S7tr6XjJZTG0Z8r8Wx3C0l43mA3Ru1HgLnsXihpRLGAwpnQTo1ixM96j9jSRKQNcLU7V
>wRxl0-FxlXp/http%3A%2F%2Fshapeblue.com%2Fcloudstack-software-engineering%2
>F>
>CloudStack Infrastructure
>SupportB9Cd0DSPp6KeDQ-BhvB-1udPqVT9gbQn7vEnhb5UcGfYe0JdWcD4QbmEIFlBLj8Q71l28tcGlp
>oOtVmXPwX4F5yIl3TzYvG9MhjvES_Oed65ElE7T-Z00kfFjSis8K61WF17ackCPr6lUpqNVr6k
>0YoCE9W/http%3A%2F%2Fshapeblue.com%2Fcloudstack-infrastructure-support%2F>
>CloudStack Bootcamp Training
>Courses_us8-YHyeYvF60c4qlZFAVKK8eaAYf7qC5CleKXru-PTZLSLmtfAs3yY5_Li4lEC8OjYFaZYEJ
>B_e79rUP7fUNdPg9rzpN37pG-r9vcCOTa_yiN3d4DVHV1dyGV3T7hoxA6JgfAc4zefEqh6-wf7
>26Q3AJw/http%3A%2F%2Fshapeblue.com%2Fcloudstack-training%2F>
>
>This email and any attachments to it may be confidential and are intended
>solely for the use of the individual to whom it is addressed. Any views
>or opinions expressed are solely those of the author and do not
>necessarily represent those of Shape Blue Ltd or related companies. If
>you are not the intended recipient of this email, you must neither take
>any action based upon its contents, nor copy or show it to anyone. Please
>contact the sender if you believe you have received this email in error.
>Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
>Services India LLP is a company incorporated in India and is operated
>under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is
>a company incorporated in Brasil and is operated under license from Shape
>Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
>South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
>is a registered trademark.

Re: Cloustack packaging

[sebgoa]

On Apr 26, 2015, at 4:34 PM, Rafael Fonseca  wrote:

> Hi Remi,
> 
> I'm building the RPMs from the latest master branch, i just referred to
> that old branch because it was the only one i found where someone was
> working on this.
> 
> Some of the issues i've encountered were:
> 
> Thsese files did not get created by the install, so
> the cloudstack-setup-management script failed.
> /etc/cloudstack/management/server-nonssl.xml
> /etc/cloudstack/management/tomcat6-nonssl.conf
> 
> Also, when this script failed it refered to a wrong log file...
> Configure CloudStack Management Server ...[Failed]
> Failed to configure CloudStack Management Server, please see the
> /var/log/cloudstack/setupManagement.log for detail
> wrong file.. correct is /var/log/cloudstack/management/setupManagement.log
> 
> Besides that, the systemd init script tries to use /usr/sbin/tomcat-sysd to
> start the service.. this file doesn't exist, only /usr/sbin/tomcat (perhaps
> it got changed in a more recent version of the tomcat rpm that is in the
> CentOS 7 repos...
> Anyway.. the current tomcat systemd script is
> calling /usr/libexec/tomcat/server and not any of those.
> If i create a symlink from /usr/sbin/tomcat-sysd to /usr/sbin/tomcat it's
> still missing the $NAME to be able to start the service.. though i can
> start it manually if I do "export NAME=cloudstack-management"
> 
> Another thing i spotted in the logs is this:
> DEBUG:root:execute:chkconfig --del tomcat6
> DEBUG:root:Failed to execute:error reading information on service tomcat6:
> No such file or directory
> 
> Which causes the cloudstack-setup-management to fail on the first run,
> after i put in the missing files.. on the second run it's fine, but the
> tomcat service is still registered in systemd ;)
> 
> Some more issues are occurring if you uninstall some packages (nothing too
> nasty, but still worth looking into) and specifically i had problems with
> reinstalling the cloudstack-management package... i didn't look much into
> that yet, but it may be related to the server not getting stopped
> automatically when i removed the packages... i needed do "rm -rf
> /usr/share/cloudstack-management/*" before i could reinstall.
> 
> I ran into a couple more issues, but these are the ones i remember off the
> top of my head or that i made some notes about.
> I'll patch it myself and submit the code for review as soon as i have some
> more time, perhaps still later today :)

Hi Rafael, welcome and thanks a lot for looking into the packaging issues.

Feel free to submit a github pull request, we can then review/comment there.
If need be we can merge your patches into a feature branch until all is fixed.

I look forward to see your changes,

-Sebastien

> 
> 
> 
> Rafael
> 
> 
> 
> 
> 
> 
> 
> On Sun, Apr 26, 2015 at 4:11 PM, Remi Bergsma  wrote:
> 
>> Hi Rafael,
>> 
>> Welcome to CloudStack and thanks for your mail.
>> 
>> What RPM packages did you use for your testing?
>> From my personal experience I know that the CentOS7 (el7) packages for
>> CloudStack 4.4 work just fine as a KVM hypervisor (on CentOS 7.1). In 4.5
>> work is done to also make it work as a Management server. So, what exact
>> problems do you run into when installing the RPM’s on CentOS 7.1?
>> 
>> As far as I know, the centos7-rpm branch is old and no longer maintained.
>> I’d recommend using the 4.5 and/or master branches instead, as these are
>> most up to date and actively maintained.
>> 
>> Feel free to send a PR to fix what you think is broken.
>> 
>> Regards,
>> Remi
>> 
>> 
>>> On 26 Apr 2015, at 15:30 , Rafael Fonseca  wrote:
>>> 
>>> Hi all,
>>> 
>>> I'm new to the cloudstack community, but i'm a seasoned developer and
>>> systems engineer and i'm sure i'll be able to help out a lot :)
>>> 
>>> I've just started on getting cloudstack running on Centos 7.1 and noticed
>>> many problems, which make it NOT work out of the box.
>>> 
>>> I'll be doing a series of fixes and submitting the code for review, since
>>> i'm not a commiter yet, if no one else is working on this.
>>> 
>>> I've seen that there's a branch called centos7-rpm which is already
>> merged
>>> with master, but there hasn't been any activity on that on the last six
>>> months, so i guess it's currently stale.
>>> 
>>> Perhaps some of these things that i spotted were working on 7.0, but i
>>> haven't tested it out on that version yet.. ideally we can make specs
>> that
>>> work on ANY 7.x version and not have a spec file for every minor release.
>>> 
>>> One of the things i immediately noticed (that is present in all
>>> centos/fedora specs, not just centos7) is the following:
>>> 
>>> %define __os_install_post %{nil}
>>> %global debug_package %{nil}
>>> 
>>> # DISABLE the post-percentinstall java repacking and line number
>> stripping
>>> # we need to find a way to just disable the java repacking and line
>> number
>>> stripping, but not the autodeps
>>> 
>>> 
>>> It's easy enough to get the __os_install_post to only do that, bu

Re: [marvin tests] interpreting results

[sebgoa]

-catching up on email after a break-

This is great to see guys, definitely we need to understand our tests better 
and expand the coverage.

With ASF purchasing more resources on Travis, this is still a very valuable 
infrastructure to run our CI/BVT until we have a different type of infra.

Speeding up the tests is also crucial, so we get feedback on each PR faster.

-sebastien

On Apr 24, 2015, at 5:14 PM, Abhinandan Prateek 
 wrote:

> Hi Gaurav,
> 
>  Your réponse will definitely help us in focusing in  the right direction.
> 
> Thanks a lot !
> -abhi
> 
> 
> 
>> On 24-Apr-2015, at 7:11 pm, Gaurav Aradhye  
>> wrote:
>> 
>> Abhi, went through the logs. The tests which have FAILED have failed because 
>> product behavior is not as expected in the test.
>> Tests with Exception seem have issue in test code.
>> 
>> Regards,
>> Gaurav Aradhye
>> 
>> On Apr 24, 2015, at 4:47 PM, Abhinandan Prateek 
>>  wrote:
>> 
>>> Attaching the logs. This is with latest 4.5 branch.
>>> 
>>> 
>>> Find out more about ShapeBlue and our range of CloudStack related services
>>> 
>>> IaaS Cloud Design & 
>>> Build
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Software 
>>> Engineering
>>> CloudStack Infrastructure 
>>> Support
>>> CloudStack Bootcamp Training 
>>> Courses
>>> 
>>> This email and any attachments to it may be confidential and are intended 
>>> solely for the use of the individual to whom it is addressed. Any views or 
>>> opinions expressed are solely those of the author and do not necessarily 
>>> represent those of Shape Blue Ltd or related companies. If you are not the 
>>> intended recipient of this email, you must neither take any action based 
>>> upon its contents, nor copy or show it to anyone. Please contact the sender 
>>> if you believe you have received this email in error. Shape Blue Ltd is a 
>>> company incorporated in England & Wales. ShapeBlue Services India LLP is a 
>>> company incorporated in India and is operated under license from Shape Blue 
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil 
>>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is 
>>> a company registered by The Republic of South Africa and is traded under 
>>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>> 
>>> 
>>> Regards,
>>> -abhi
>>> 
>>> 
 On 24-Apr-2015, at 4:21 pm, Gaurav Aradhye  
 wrote:
 
 Hi Abhi,
 
 FAILED indicates it’s an assertion error. Even if the test case is 
 expecting a failure, it must have been written in such a way that when an 
 operation fails, test case passes.
 Here it indicates that operation which should have failed has succeeded, 
 might be a product issue.
 
 Exception indicates there is an unexpected exception in the code, other 
 than assertions.
 
 Can you please share the detailed logs from failed_plus_exceptions.txt 
 file in the log folder?
 
 Regards,
 Gaurav Aradhye
 
 On Apr 24, 2015, at 4:04 PM, Abhinandan Prateek 
  wrote:
 
> 
> Have been trying to run some marvin test cases. Need to know how to 
> interpret the result.
> 
> On running test cases I see several success and failure messages. Lets 
> take example of each from output of
> /root/cloudstack/test/integration/component/test_acl_isolatednetwork.py 
> on ACS 4.5, taking a sample from output:
> 
> === TestName: test_02_createNetwork_admin_foruserinsamedomain | Status : 
> SUCCESS ===
> 
> ***The above says the test case is successful, basically the 
> functionality works.
> 
> === TestName: test_09_createNetwork_user_foruserinsamedomain | Status : 
> FAILED ===
> 
> ***From the code it appears that the test is expected to fail, this also 
> means the test case is successful.
> 
> === TestName: test_12_deployvm_admin_foruserinsamedomain | Status : 
> EXCEPTION ===
> 
> I assume this means the test case did not execute successfully ? If 
> it is on a fresh environment will that mean something is wrong with the 
> test itself ?
> 
> Can someone share some gyan on above ?
> 
> -abhi
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & 
> Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Enginee

Re: [DISCUSS] 4.6 release management

[sebgoa]

On Apr 22, 2015, at 12:24 PM, Raja Pullela  wrote:

> Sebastien, I am taking about the tests we have under "test/integration/smoke" 
> folder.  
> Not sure how the tests run through Travis, will try to understand.
> These are tests were run on a local cloudstack env.  
> 

Just catching up and making sure I reply to Raja here.

Travis (https://travis-ci.org) runs those tests, by building cloudstack and 
running the simulator.
All the travis setup is defined in the travis.yml file in the root of the repo.
This setup can probably be improved.

Do note that if you fork on your own github, pushes to your own branch will run 
through Travis as well.


> best,
> Raja
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: Friday, April 17, 2015 1:14 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] 4.6 release management
> 
> 
>> On Apr 17, 2015, at 6:26 AM, Raja Pullela  wrote:
>> 
>> +1 for the "Some people (I'm part of them) are concerned on our current way 
>> of supporting and back porting fixes to multiple release"
>> This should be a top priority along with keeping master stable - make sure 
>> BVTs are passing at 100% all the time.
> 
> Raja, which BVT are you talking about ? AFAIK, all current tests run on all 
> commits through Travis.
> 
>> Also if we can plan/target increasing test/BVT coverage, that will be super!
>> 
>> Thanks,
>> Raja
>> -Original Message-
>> From: Marcus [mailto:shadow...@gmail.com]
>> Sent: Friday, April 17, 2015 4:35 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] 4.6 release management
>> 
>> "storage plugin involve changes on Hypervisor code"
>> 
>> I know this is just an example, but at least on KVM side this is no longer 
>> true. Previously you had to implement a KVM-specific 'StorageAdaptor' that 
>> would run on the hypervisor, and register that with the agent code, but Mike 
>> and I added some reflection/annotation that allows for auto-detection of the 
>> adaptor upon Agent start up, so storage plugins can be completely 
>> self-contained now. They don't even have to be a part of our code base.
>> 
>> There may be other parts of the code where we can do similar things to 
>> decouple if we can identify those points.  Ideally, if someone has to modify 
>> core code to add their plugin it should only be because they are adding some 
>> new functionality *that core cloudstack needs to be aware of*, and that 
>> functionality should be added in a way that other plugins can also 
>> provide/implement it. Otherwise, they can always add new APIs specific to 
>> their appliance or product and leveraging data from cloudstack's db, all via 
>> plugin. They can add new global/zone/cluster configs and UI tools via plugin 
>> as well.
>> 
>> On Thu, Apr 16, 2015 at 3:49 PM, Pierre-Luc Dion  wrote:
>>> Today during the CloudStackdays  we did a round table about Release 
>>> management targeting the next 4.6 releases.
>>> 
>>> 
>>> Quick bullet point discussions:
>>> 
>>> ideas to change release planning
>>> 
>>>  - Plugin contribution is complicated because often  a new plugin involve
>>>  change on the core:
>>> - ex: storage plugin involve changes on Hypervisor code
>>>  - There is an idea of going on a 2 weeks release model which could
>>>  introduce issue the database schema.
>>>  - Database schema version should be different then the application
>>>  version.
>>>  - There is a will to enforce git workflow in 4.6  and trigger simulator
>>>  job on  PullRequest.
>>>  - Some people (I'm part of them) are concerned on our current way of
>>>  supporting and back porting fixes to multiple release (4.3.x, 4.4.x,
>>>  4.5.x). But the current level of confidence against latest release is low,
>>>  so that need to be improved.
>>> 
>>> 
>>> So, the main messages is that w'd like to improve the release 
>>> velocity, and release branch stability.  so we would like to propose 
>>> few change in the way we would add code to the 4.6 branch as follow:
>>> 
>>> - All new contribution to 4.6 would be thru Pull Request or merge 
>>> request, which would trigger a simulator job, ideally only if that 
>>> pass the PR would be accepted and automatically merged.  At this 
>>> time, I think we pretty much have everything in place to do that. At 
>>> a first step we would use
>>> simulator+marvin jobs then improve tests coverage from there.
>>> 
>>> Please comments :-)
> 

Re: [DISCUSS] 4.6 release management

[sebgoa]

On Apr 20, 2015, at 4:12 PM, S. Brüseke - proIO GmbH  
wrote:

> Hi all,
> 
> it is really hard for a newbie to follow all of your thought regarding this. 
> Can somebody please explain it a little bit more?
> Thank you very much!
> 

Hi Swen,

I will try.

Currently we develop cloudstack in the master branch, and create a 'release' 
branch for major releases.
Hence we have a 4.3 branch, a 4.4 branch etc….

We are currently on 4.5 , which means that what is master now will become our 
4.5 release.

The issue comes when stabilizing a release branch.

A traditional approach would hand off the release branch to a QA team and let 
the QA team harden that branch over several months. This tends to make each 
release a somewhat different product of each other.  It also creates a 
maintenance headache, as we have to abandon branches. We do not want anyone to 
feel abandoned on some dead branches, thus we maintain upgrade paths that can 
become complex, with fixes and features that can't be merged in various 
branches and regressions. Bottom line:

headache, heartache, nightmares, no fun.

This is not something specific to cloudstack and other projects face similar 
issues.

I am of the opinion that for our community this is not a workable model, as we 
do not have a dedicated QA team. Even though some of us are paid to work on 
CloudStack.

So we are talking about finding a better release management model, that would 
allow us to release faster and more stable software (not to say that it is 
unstable right now, just that things can be improved).

One model among many, would be to treat master as our release branch and merge 
features/fixes into master once we know they are valid and do not break 
anything. This would increase our trust in master as production software and 
put us on a path of continuous deployment with an iterative/rolling upgrade 
mindset.

Since all committers have write access to master, treating master as a release 
branch (for example), involves all of us reaching consensus and agreeing that a 
release manager will be the only one allowed to touch that branch (for 
instance). This also involves being able to release much faster (which we have 
to do official through manual votes for legal purposes), reducing scope of each 
release etc….

I hope that clarifies things a bit,

-Sebastien

> Mit freundlichen Grüßen / With kind regards,
> 
> Swen Brüseke
> 
> -Ursprüngliche Nachricht-
> Von: Simon Weller [mailto:swel...@ena.com] 
> Gesendet: Montag, 20. April 2015 15:24
> An: dev@cloudstack.apache.org
> Betreff: Re: [DISCUSS] 4.6 release management
> 
>> 
>> From: Sebastien Goasguen 
>> Sent: Saturday, April 18, 2015 2:50 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] 4.6 release management
> 
>> On Apr 18, 2015, at 8:36 AM, Marcus  wrote:
>> 
>> Have they diverged that much? Due to cherry-picking, I guess.
>> Otherwise you should be able to do it cleanly.
>> 
>> There's a good opportunity to do this next release. Instead of 
>> creating a release branch, we freeze master and start creating dev 
>> branches.
> 
>> +1
> 
>> This just amounts to treating master now like a release branch. Getting 
>> back to PL suggestion, that means that any commit to master would be through 
>> a PR or MERGE request on the ML. Anything else will be reverted by the >RM.
> 
> +1 on this.
> 
> Ultimately this will be painful to start with, but it will pay dividends in 
> the future with a much more stable (and tested) master, and hence future 
> releases will be of higher quality. 
> With stable (and frequent iterative) releases, there will be much less 
> pressure to back port fixes/features, because the community will see taking a 
> new release as low risk.
> 
> - Si
> 
>> Marcus, do you feel like writing down a little process for this and some 
>> dates that we can target.
>> It would be nice to do this for 4.6.
> 
>> 
>> On Fri, Apr 17, 2015 at 10:46 PM, Daan Hoogland  
>> wrote:
>>> We heavily invested in code now on master. Not looking forward to 
>>> backporting that.
>>> 
>>> mobile dev with bilingual spelling checker used (read at your own 
>>> risk) Op 17 apr. 2015 21:02 schreef "Marcus" :
>>> 
 Well, would we just swap the last release branch with master? Master 
 is the dev branch, and the last release is really what we have as a 
 stable branch.
 
 On Fri, Apr 17, 2015 at 8:44 AM, Daan Hoogland 
 
 wrote:
> On Fri, Apr 17, 2015 at 2:43 AM, Sebastien Goasguen 
> 
 wrote:
>> 
>>> On Apr 17, 2015, at 12:49 AM, Pierre-Luc Dion 
>>> 
 wrote:
>>> 
>>> Today during the CloudStackdays  we did a round table about 
>>> Release management targeting the next 4.6 releases.
>>> 
>>> 
>>> Quick bullet point discussions:
>>> 
>>> ideas to change release planning
>>> 
>>> - Plugin contribution is complicated because often  a new plugin
 involve
>>> change

Jenkins build is still unstable: simulator-singlerun #1156

[jenkins]

See 

Re: Marvin Error

[Ian Southam]

On 28 Apr 2015, at 14:52, Srikanteswararao Talluri 
mailto:srikanteswararao.tall...@citrix.com>>
 wrote:

Yeah, it is available post 2.7.9, Its my bad to use the private variable
from module. I¹ll see If I can fix that.

Yes indeed using 2.7.9 does indeed make the problem go away!

For now that works for me ;).

Thanks for the reply.

—
Grts!
Ian

Re: [DISCUSS] name for google API interface

[Mike Tutkowski]

How's about awesomegstack? ;)

On Tuesday, April 28, 2015, Sebastien Goasguen  wrote:

> Folks,
>
> The GCE API wrapper that Ian, Darren and myself are working on giving to
> cloudstack has a name ‘gstack’ which is currently in use by:
> http://linux.die.net/man/1/gstack
>
> Bit silly to have use that name but blame it on me.
>
> We originally called it gcloud, but then Google renamed it’s CLI gcloud
> and we had to switch.
>
> For IP clearance we need to show best effort at using a name that is not
> in use.
>
> Any thoughts on a new name ?
>
> gceapi ?
> gcestack ?
>
> -sebastien



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

Jenkins build is still unstable: simulator-4.5-singlerun #222

[jenkins]

See 

[GitHub] cloudstack pull request: fix CLOUDSTACK-8402

[giraffeforestg]

Github user giraffeforestg commented on the pull request:

https://github.com/apache/cloudstack/pull/192#issuecomment-97106698
  
I once closed.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: fix CLOUDSTACK-8402

[giraffeforestg]

Github user giraffeforestg closed the pull request at:

https://github.com/apache/cloudstack/pull/192


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: fix CLOUDSTACK-8402

[giraffeforestg]

GitHub user giraffeforestg opened a pull request:

https://github.com/apache/cloudstack/pull/205

fix CLOUDSTACK-8402

https://issues.apache.org/jira/browse/CLOUDSTACK-8402

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/giraffeforestg/cloudstack fix_CLOUDSTACK-8402

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/205.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #205


commit b19370f0f0fd897e2356a55dc284e9f3ac6a13ff
Author: Satoru Nakaya 
Date:   2015-04-28T15:43:03Z

fix CLOUDSTACK-8402




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[DISCUSS] State of 4.5 and testing in local environments

[Rohit Yadav]

Hi all,

### 4.5 Release Effort

I’ve been exhaustively testing ACS 4.5 wrt Xen 6.2, Xen 6.5, KVM (qemu 2.0, 
2.3) and I feel we’re pretty good but we need testing efforts and I want to 
help drive efforts to releasing ACS 4.5.1 -- if you’ve any issues that you 
would like to get fixed that are either regressions or blockers can you please 
share on this thread? If we don’t find any blockers or regressions let us 
invest in ACS 4.5 testing and release it soon. For other minor issues we can 
always fix them and release 4.5.2 etc if and when needed in future.

Regarding my 4.5 testing - I’ve tested basic vm life cycle operations (deploy, 
start, stop, destroy/expunge, migrate to another host, migrate to another 
storage pool, deploy using iso) for all cases and found no issues;

KVM with basic zone (with/without security groups, SG blockers were found and 
fixed)
KVM with Adv zone (with/without security groups, both isolated network and VPC 
worked, networking issues were found and fixed)
XenServer 6.2 with basic and adv zones (with/without security groups, no SG 
issues found)
XenServer 6.5 with basic and adv zones (with/without security groups, SG 
blockers found and fixed)

I found one issue that could be a blocker (if it’s not a hardware/env issue) -- 
when using security groups in advance zone with a dedicated vlan id (say 
vlan://500), I was unable to access the VMs (CPVM, SSVM, VR or user vms) though 
all normal vm_life cycles seems to work. Though this worked for me when I used 
the vlan://untagged. I tried to add vlan id 500 to my local nics using vconfig 
but I still was n’t able to do access the CPVM or user VMs. I guess my 
understanding of vlans with security groups is limited, so if anyone knows 
about this feature or has used it - please help with some regression testing. I 
plan to continue testing this week with VMWare and fix any issues we find.


### Testing against Xen, KVM, VMWare etc.

With a recent improvement to allow cpu features (such as vmx) on KVM hosts 
(https://github.com/apache/cloudstack/commit/58cc569273905c50d089f9fd82fe80028b4e9775),
 it’s now possible to run KVM, ESX, XenServer, OVM3 (LXC, and hopefully others) 
on KVM (in case of ESX a patched qemu would be needed: 
http://people.apache.org/~bhaisaab/qemu/). Such a (ansible based) tool aims to 
be reproduce such an environment for anyone and serve as a developer kit (not 
to be confused with the DevCloud appliance, will share more details of the 
developer kit later) and as an infrastructure to run integration testing suite 
we have now. This would allow us to build/test/run CloudStack against various 
nested-virtualized hosts running as guests on KVM, using CloudStack.

Meanwhile, Abhi is focusing on existing (integration) tests and has increased 
the number of TravisCI tests: 
https://travis-ci.org/apache/cloudstack/builds/60365947

Our goal with these efforts is to (1) have a developer kit that a developer can 
have locally to build/test/develop CloudStack, (2) scale it up for bigger 
baremetal servers to run long running integration tests and have a better QA 
automation.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: [DISCUSS] 4.6 release management

[ilya]

Rohit

Any headway on ESX 5.5? I've done this many times before using 
cloudstack and esx, but i was using esx as parent hypervisor.


The challenge for me was being able to automatically deploy and 
configure the vSphere + ESXi env. I managed to get the whole flow 
working with bash script, puppet, VMA and while it works its not pretty. 
The challenge was the networking bit.


Last but not least, consider using cloudstack to test cloudstack. i.e. 
master env, would use cloudstack projects and spinup smaller envs with 
KVM, Xen and VmWare bound to each project.


Regards
ilya

On 4/24/15 7:53 AM, Rohit Yadav wrote:

Daan,


On 24-Apr-2015, at 3:53 pm, Daan Hoogland  wrote:

Rohit, the issues you mention are not as painful if we release in a
two week schedule as the period of creating a fix to seeing it in a
release will be shorter. Some releases will be broken for some people,
I don't think we can prevent this. The target we are aiming for is to
big to cover it completely.

I agree with you, but I think there are pros and cons to both approaches and 
for this to work it needs to be able to walk first before it can run.

For this to work we need an automated QA system, to solve this Abhi is working 
on it for past few weeks and will be adding more non-hardware tests (simulator 
ones) to travis. In my free time, I’m trying to setup a nested virtualized 
environment where we can test ACS against Xen, KVM and VMware on top on KVM. So 
far, I’m able to run XenServer 6.2+6.5 and KVM on top of KVM with vmx 
(intel-vt) enabled, and making some progress with running ESX on KVM (I’m able 
to run ESX 6.0 on KVM now, but not ESX 5.x which is something I’m exploring). I 
hope we'll have something working soon that is fairly fast and easy to 
reproduce.


Your points are valid, though.
.1 a three person release team makes sense. I have been really happy
with the help I got from Pierre-Luc and I think David can do with help
the coming time as well.
.2 Hopefully people won't need to test every release so extensively
anymore as the changes become smaller. (and my initial remark the
above applies as well)

By having too many releases we’ll have to deal with too many upgrade path 
issues and users will spread across different versions which will create an 
issue for maintainers who are supporting users -- one solution for this problem 
can be that we introduce a concept of LTS release that is either maintained by 
the community (which can be difficult) or some interested stakeholders, for 
users that would prefer upgrading everytime there is a new CloudStack release.


On Fri, Apr 24, 2015 at 2:43 PM, Rohit Yadav  wrote:

I think we need to have a faster release management to speed up process in 
general, and for that I propose that we have at least two co-pilots for the 
release manager who would support them with things like reviewing/merging 
patches, creating RC candidates etc whenever necessary. Having only one person 
as a release manager can become a bottleneck for a speedy release.

The other issue is getting people to test a (release) branch, fix bugs and 
expect a review/result in 72 hours. This has usually failed if people are busy 
and not getting enough time for this. As an example, I think 4.5 is delayed 
because it lacked people actively testing it or fixing issues, or when issues 
were found only around the RC testing period which delayed RC voting by 1-2 
weeks every time that happened. (I’ll post details about where I think we are 
wrt 4.5 in another thread).


On 17-Apr-2015, at 12:49 am, Pierre-Luc Dion  wrote:

Today during the CloudStackdays  we did a round table about Release
management targeting the next 4.6 releases.


Quick bullet point discussions:

ideas to change release planning

  - Plugin contribution is complicated because often  a new plugin involve
  change on the core:
 - ex: storage plugin involve changes on Hypervisor code
  - There is an idea of going on a 2 weeks release model which could
  introduce issue the database schema.
  - Database schema version should be different then the application
  version.
  - There is a will to enforce git workflow in 4.6  and trigger simulator
  job on  PullRequest.
  - Some people (I'm part of them) are concerned on our current way of
  supporting and back porting fixes to multiple release (4.3.x, 4.4.x,
  4.5.x). But the current level of confidence against latest release is low,
  so that need to be improved.


So, the main messages is that w'd like to improve the release velocity, and
release branch stability.  so we would like to propose few change in the
way we would add code to the 4.6 branch as follow:

- All new contribution to 4.6 would be thru Pull Request or merge request,
which would trigger a simulator job, ideally only if that pass the PR would
be accepted and automatically merged.  At this time, I think we pretty much
have everything in place to do that. At a first step we would use
simulator+marvin jobs then improve tests coverage

Jenkins build is still unstable: simulator-singlerun #1157

[jenkins]

See 

Jenkins build is still unstable: simulator-4.5-singlerun #223

[jenkins]

See 

Re: [DISCUSS] 4.6 release management

[Rohit Yadav]

Hi Ilya,

In short - to run ESX and other hypervisors (Xen, KVM, OVM3, HyperV etc) on KVM 
you need to;

- use patched qemu (tested to work on both Ubuntu 14.04 and 15.04 x64, I’m 
waiting for Fedora 22 to test it on F22 as well), you may install the pre-built 
debs or build/install qemu from source using the patch from here: 
people.apache.org/~bhaisaab/qemu
- use ACS using latest 4.5 branch and deploy a basic zone (without SG) to 
provision hypervisor hosts as user vms
- in agent.properties (on your kvm host), enable guest.cpu.features=vmx and 
guest.cpu.mode=host-passthrough
- when deploying ESX 5.x on vm (or installing using an ISO) deploy 
virtualmachine with details nicAdapter=vmxnet3, for other hypervisors 
(including ESX 6.0) E1000, the default nic adapter, works

IMO this is a better approach as it does not depend on ESX or VMWare fusion 
that requires special hardware (vCenter/Windows etc or OSX/Apple machine) and 
are difficult to automate. Working with KVM host, since is a Linux machine, 
would be more familiar to sysadmins and certainly a pleasure to scale and work 
with because one can avoid management tools (such as XenCenter or vCenter).

(I’m still working on the "CloudStack Developer Kit” {CDK} so it’s not in a 
state to be released yet, will avoid publishing a faulty tool now. Instead of 
the DevCloud approach which promotes everything on one machine, the CDK I’m 
trying to build focuses on developer productivity, reproducibility and 
scalability of a QA lab, it recommends at least one companion hardware with a 
developer’s workstation/laptop which can be a small-form-factor server like a 
mini PC or NUC with at least 16GB RAM and 4 cores i7 with Intel VT. Hope to 
share it soon.)

> On 28-Apr-2015, at 7:17 pm, ilya  wrote:
>
> Rohit
>
> Any headway on ESX 5.5? I've done this many times before using cloudstack and 
> esx, but i was using esx as parent hypervisor.
>
> The challenge for me was being able to automatically deploy and configure the 
> vSphere + ESXi env. I managed to get the whole flow working with bash script, 
> puppet, VMA and while it works its not pretty. The challenge was the 
> networking bit.
>
> Last but not least, consider using cloudstack to test cloudstack. i.e. master 
> env, would use cloudstack projects and spinup smaller envs with KVM, Xen and 
> VmWare bound to each project.
>
> Regards
> ilya
>
> On 4/24/15 7:53 AM, Rohit Yadav wrote:
>> Daan,
>>
>>> On 24-Apr-2015, at 3:53 pm, Daan Hoogland  wrote:
>>>
>>> Rohit, the issues you mention are not as painful if we release in a
>>> two week schedule as the period of creating a fix to seeing it in a
>>> release will be shorter. Some releases will be broken for some people,
>>> I don't think we can prevent this. The target we are aiming for is to
>>> big to cover it completely.
>> I agree with you, but I think there are pros and cons to both approaches and 
>> for this to work it needs to be able to walk first before it can run.
>>
>> For this to work we need an automated QA system, to solve this Abhi is 
>> working on it for past few weeks and will be adding more non-hardware tests 
>> (simulator ones) to travis. In my free time, I’m trying to setup a nested 
>> virtualized environment where we can test ACS against Xen, KVM and VMware on 
>> top on KVM. So far, I’m able to run XenServer 6.2+6.5 and KVM on top of KVM 
>> with vmx (intel-vt) enabled, and making some progress with running ESX on 
>> KVM (I’m able to run ESX 6.0 on KVM now, but not ESX 5.x which is something 
>> I’m exploring). I hope we'll have something working soon that is fairly fast 
>> and easy to reproduce.
>>
>>> Your points are valid, though.
>>> .1 a three person release team makes sense. I have been really happy
>>> with the help I got from Pierre-Luc and I think David can do with help
>>> the coming time as well.
>>> .2 Hopefully people won't need to test every release so extensively
>>> anymore as the changes become smaller. (and my initial remark the
>>> above applies as well)
>> By having too many releases we’ll have to deal with too many upgrade path 
>> issues and users will spread across different versions which will create an 
>> issue for maintainers who are supporting users -- one solution for this 
>> problem can be that we introduce a concept of LTS release that is either 
>> maintained by the community (which can be difficult) or some interested 
>> stakeholders, for users that would prefer upgrading everytime there is a new 
>> CloudStack release.
>>
>>> On Fri, Apr 24, 2015 at 2:43 PM, Rohit Yadav  
>>> wrote:
 I think we need to have a faster release management to speed up process in 
 general, and for that I propose that we have at least two co-pilots for 
 the release manager who would support them with things like 
 reviewing/merging patches, creating RC candidates etc whenever necessary. 
 Having only one person as a release manager can become a bottleneck for a 
 speedy release.

 The ot

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[bhaisaab]

Github user bhaisaab commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29279216
  
--- Diff: 
engine/storage/image/src/org/apache/cloudstack/storage/image/store/TemplateObject.java
 ---
@@ -28,7 +28,6 @@
 import 
org.apache.cloudstack.engine.subsystem.api.storage.DataObjectInStore;
 import org.apache.cloudstack.engine.subsystem.api.storage.DataStore;
 import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine;
-import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine.Event;
--- End diff --

It's not a compilation error but removing this import cause a variable 
definition to use the whole import path.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Cloudstack 4.4.3 rpm location question

[Chandler Vaughn]

Hi everyone. Does anyone happen to know where I can pull rpms? I tried the link 
in the announcement (below) but didn’t see 4.4.3 in there. Please let me know 
if I’m just not seeing it.

* RPM package repository: 
http://cloudstack.apt-get.eu/rhel/


Chandler Vaughn
SVP, Product Development
cvau...@codero.com
(TEL) 913.890.7770
(FAX) 913.890.7701

Re: Cloudstack 4.4.3 rpm location question

[Rohit Yadav]

You can get 4.4.3 rpms etc. from here:
http://shapeblue.com/packages/

> On 28-Apr-2015, at 10:28 pm, Chandler Vaughn  wrote:
>
> Hi everyone. Does anyone happen to know where I can pull rpms? I tried the 
> link in the announcement (below) but didn’t see 4.4.3 in there. Please let me 
> know if I’m just not seeing it.
>
> * RPM package repository: 
> http://cloudstack.apt-get.eu/rhel/
>
>
> Chandler Vaughn
> SVP, Product Development
> cvau...@codero.com
> (TEL) 913.890.7770
> (FAX) 913.890.7701

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Build failed in Jenkins: build-systemvm-master #511

[jenkins]

See 

Changes:

[sanjay.tripathi] CLOUDSTACK-8410. ESXi host stuck disconnects frequently.

[likitha.shetty] CLOUDSTACK-8411. Unable to delete an uploaded volume after CCP 
fails to attach the volume to a VM.

[likitha.shetty] CLOUDSTACK-8412. VM migration with storage fails.

[Gaurav Aradhye] CLOUDSTACK-8394: Skip test cases through setUp() instead of 
setUpClass()

[Rohit Yadav] CLOUDSTACK-8424: Add cpu features if guest.cpu.features is set

[abhinandan.prateek] adding self service tests to increase coverage

[Rohit Yadav] marvin: set ssl cert verification only if ssl module supports it

[Rohit Yadav] kvm: add VMXNET3 nic adapter to nic models

--
[...truncated 1075 lines...]
+ '[' -t 2 ']'
+ echo '[2015-04-28 21:55:10] INFO: destroying existing veewee image, if any'
[2015-04-28 21:55:10] INFO: destroying existing veewee image, if any
+ set +e
+ bundle exec veewee vbox destroy systemvmtemplate-master-4.6.0
Error:: You tried to destroy a non-existing box 'systemvmtemplate-master-4.6.0'
+ set -e
+ add_on_exit veewee_destroy
+ local n=3
+ on_exit_items[${n}]=veewee_destroy
+ '[' 3 -eq 0 ']'
+ veewee_build
+ log INFO 'building new image with veewee'
+ local level=INFO
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2015-04-28 21:55:12] INFO: building new image with veewee'
+ '[' -t 2 ']'
+ echo '[2015-04-28 21:55:12] INFO: building new image with veewee'
[2015-04-28 21:55:12] INFO: building new image with veewee
+ bundle exec veewee vbox build systemvmtemplate-master-4.6.0 --nogui --auto
Downloading vbox guest additions iso v 4.3.14 - 
http://download.virtualbox.org/virtualbox/4.3.14/VBoxGuestAdditions_4.3.14.iso
Checking if isofile VBoxGuestAdditions_4.3.14.iso already exists.
Full path: 


   
Fetching file:   0% |  | ETA:  --:--:--
Fetching file:   1% || 644.5KB   4.9MB/s ETA:   0:00:12
Fetching file:   2% ||   1.3MB   5.9MB/s ETA:   0:00:10
Fetching file:   3% ||   1.9MB   6.3MB/s ETA:   0:00:09
Fetching file:   4% ||   2.5MB   4.2MB/s ETA:   0:00:14
Fetching file:   5% |o   |   3.1MB   4.6MB/s ETA:   0:00:12
Fetching file:   6% |o   |   3.8MB   5.0MB/s ETA:   0:00:11
Fetching file:   7% |o   |   4.4MB   5.4MB/s ETA:   0:00:10
Fetching file:   8% |o   |   5.0MB   5.6MB/s ETA:   0:00:10
Fetching file:   9% |oo  |   5.7MB   5.9MB/s ETA:   0:00:09
Fetching file:  10% |oo  |   6.3MB   5.8MB/s ETA:   0:00:09
Fetching file:  11% |oo  |   6.9MB   5.7MB/s ETA:   0:00:09
Fetching file:  12% |oo  |   7.5MB   5.7MB/s ETA:   0:00:09
Fetching file:  13% |ooo |   8.2MB   5.7MB/s ETA:   0:00:09
Fetching file:  14% |ooo |   8.8MB   5.8MB/s ETA:   0:00:09
Fetching file:  15% |ooo |   9.4MB   5.8MB/s ETA:   0:00:09
Fetching file:  16% |ooo |  10.1MB   5.9MB/s ETA:   0:00:08
Fetching file:  17% ||  10.7MB   5.4MB/s ETA:   0:00:09
Fetching file:  18% ||  11.3MB   5.3MB/s ETA:   0:00:09
Fetching file:  19% ||  12.0MB   5.2MB/s ETA:   0:00:09
Fetching file:  20% ||  12.6MB   5.2MB/s ETA:   0:00:09
Fetching file:  21% |o   |  13.2MB   5.2MB/s ETA:   0:00:09
Fetching file:  22% |o   |  13.8MB   5.2MB/s ETA:   0:00:09
Fetching file:  23% |o   |  14.5MB   5.2MB/s ETA:   0:00:09
Fetching file:  24% |o   |  15.1MB   5.3MB/s ETA:   0:00:09
Fetching file:  25% |oo  |  15.7MB   5.3MB/s ETA:   0:00:08
Fetching file:  26% |oo  |  16.4MB   5.3MB/s ETA:   0:00:08
Fetching file:  27% |oo  |  17.0MB   5.4MB/s ETA:   0:00:08
Fetching file:  28% |oo  |  17.6MB   5.4MB/s ETA:   0:00:08
Fetching file:  29% |oo  |  18.2MB   5.5MB/s ETA:   0:00:08
Fetching file:  30% |ooo |  18.9MB   5.5MB/s ETA:   0:00:07
Fetching file:  31% |ooo |  19.5MB   5.6MB/s ETA:   0:00:07
Fetching file:  32% |ooo |  20.1MB   5.7MB/s ETA:   0:00:07
Fetching file:  33% |ooo |  20.8MB   5.7MB/s ETA:   0:00:07
Fetching file:  34% ||  21.4MB   5.8MB/s ETA:   0:00:07
Fetching file:  35% ||  22.0MB   5.8MB/s ETA:   0:00:07
Fetching file:  36% ||  22.6MB   5.9MB/s ETA:   0:00:

Re: [4.6] Trouble with virtual router

[Mike Tutkowski]

Unfortunately I'm not able to make out any errors on the console.

Is there something within the VM's OS that I can look at to debug this?

I see that SSVM and CPVM have IP addresses, but the VR does not.

Any hints would be great as unfortunately I had to postpone a CloudStack
demo for a potential customer today due to this issue.

Thanks!

On Tue, Apr 28, 2015 at 4:24 AM, Sanjeev N  wrote:

> One of the reasons for VR not to come up is, once CS creates VR on
> hypervisor, it does a ping on VR's management interface for centain no.of
> of times. If it does not receive any response then it will shut down the
> VR.
>
> So when VR is coming up check its console and see any network issues.
>
> On Tue, Apr 28, 2015 at 12:39 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Huh...it doesn't work on KVM either (this is on Ubuntu 14.04). The
> failure
> > is a bit different, though. In this case, the SSVM stays in the Running
> > state, but the agent doesn't seem to ever come up.
> >
> > Oh well...I guess I'll try ESXi later.
> >
> > On Mon, Apr 27, 2015 at 11:45 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > Thanks for the message, Abhi.
> > >
> > > I went ahead and deleted the host tag from each of my XenServer hosts
> > > (it's a new environment, so I only had one host tag per host). I then
> > > performed a force reconnect on each host.
> > >
> > > Unfortunately, I still seem to be encountering the same issue (even
> after
> > > destroying and re-creating the VR). This seems broken on both XenServer
> > 6.2
> > > and XenServer 6.1.
> > >
> > > I think I will give it a try with ESXi 5.1 or KVM. I'm mainly
> interested
> > > in dealing with XenServer (for the time being) for this particular
> > feature
> > > I'm working on, but perhaps I can at least get the system VMs up and
> > > running on another hypervisor to allow me to move forward.
> > >
> > > On Mon, Apr 27, 2015 at 11:23 PM, Abhinandan Prateek <
> > > abhinandan.prat...@shapeblue.com> wrote:
> > >
> > >> Had similar problem where SSVM and CPVM came up but not the VR.
> > >> In my case I traced it to systemvm.iso not getting updated on
> XenServer,
> > >> due to the old host-tag.
> > >> On deleting the host tag the MS was able to copy the systemvm.iso to
> Xen
> > >> and things were fine after that.
> > >>
> > >> -abhi
> > >>
> > >>
> > >> > On 28-Apr-2015, at 10:15 am, Mike Tutkowski <
> > >> mike.tutkow...@solidfire.com> wrote:
> > >> >
> > >> > Hi,
> > >> >
> > >> > Tonight I tried to re-create a cloud from scratch and made use of
> the
> > >> > following system template:
> > >> >
> > >> >
> > >>
> >
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
> > >> >
> > >> > My SSVM and CPVM get IP addresses and seem to behave OK; however, my
> > VR
> > >> > never gets into the Running state. It gets to a point and then is
> > >> restarted
> > >> > (this happens a couple times). Eventually CS gives up on it.
> > >> >
> > >> > I only have two XenServer 6.2 hosts in this environment. The system
> > VMs
> > >> are
> > >> > running on local storage.
> > >> >
> > >> > Thoughts on this?
> > >> >
> > >> > Thanks!
> > >> >
> > >> > --
> > >> > *Mike Tutkowski*
> > >> > *Senior CloudStack Developer, SolidFire Inc.*
> > >> > e: mike.tutkow...@solidfire.com
> > >> > o: 303.746.7302
> > >> > Advancing the way the world uses the cloud
> > >> > *™*
> > >>
> > >> Find out more about ShapeBlue and our range of CloudStack related
> > services
> > >>
> > >> IaaS Cloud Design & Build<
> > >> http://shapeblue.com/iaas-cloud-design-and-build//>
> > >> CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/
> > >
> > >> CloudStack Consulting
> > >> CloudStack Software Engineering<
> > >> http://shapeblue.com/cloudstack-software-engineering/>
> > >> CloudStack Infrastructure Support<
> > >> http://shapeblue.com/cloudstack-infrastructure-support/>
> > >> CloudStack Bootcamp Training Courses<
> > >> http://shapeblue.com/cloudstack-training/>
> > >>
> > >> This email and any attachments to it may be confidential and are
> > intended
> > >> solely for the use of the individual to whom it is addressed. Any
> views
> > or
> > >> opinions expressed are solely those of the author and do not
> necessarily
> > >> represent those of Shape Blue Ltd or related companies. If you are not
> > the
> > >> intended recipient of this email, you must neither take any action
> based
> > >> upon its contents, nor copy or show it to anyone. Please contact the
> > sender
> > >> if you believe you have received this email in error. Shape Blue Ltd
> is
> > a
> > >> company incorporated in England & Wales. ShapeBlue Services India LLP
> > is a
> > >> company incorporated in India and is operated under license from Shape
> > Blue
> > >> Ltd. Shape Bl

[WWW] CloudStack days Dublin event is 404

[Jan-Arve Nygård]

Hi,

Not sure who the correct recipient would be so i'm posting this here:

1 . The link (http://events.linuxfoundation.org/events/cloudstack-dublin)
to the CloudStack days Dublin event on cloudstack.apache.org is 404.

This could be because the event was changed to a 2-day event but this
should be fixed. I guess the second date should be added as well.

2. Several of the new committers seems to be missing on the list of
committers on cloudstack.apache.org. If the source is available somewhere i
could help with updating the list if someone points me in the right
direction.


Thanks,

-thinktwo

[4.6] VMware System Template

[Mike Tutkowski]

Hi,

Is the current 4.6 system template working for anyone?

I get an error when VmwareStorageManagerImpl tries to un-tar it.

When I run the following manually, I get an error message saying that the
OVA doesn't look like a tar archive:

tar --no-same-owner -xf 

Thoughts?

Thanks,

-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
*™*

[GitHub] cloudstack pull request: fix CLOUDSTACK-8402

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/205


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [MERGE] Browser based template or volume upload

[Rajani Karuturi]

Hi Daan,

I will resolve the conflicts and will put up another pull request. Though
travis is green, looks like it ran on the branch instead of after doing the
merge.

Thanks,

~Rajani

On Tue, Apr 28, 2015 at 1:05 PM, Daan Hoogland 
wrote:

> Rajani et al,
>
> Great effort. Apache jenkins doesn't merge the pull request cleanly so
> maybe a more careful manual merge is required. please go ahead. Travis
> is fine and of course always right;)
>
> On Tue, Apr 28, 2015 at 8:20 AM, Rajani Karuturi 
> wrote:
> > We worked on below proposal for Browser based template or volume upload.
> > development effort from @bvbharat, Koushik Das and @karuturi
> > UI help from @bfederle , Jessica Wang and @rags22489664
> > testing effort from Deepthi Machiraju and @sailajamada
> >
> > We believe this feature is ready to merge. If you have any
> > objections/suggestions/comments, please let us know before tomorrow.
> >
> > Proposal discussion: http://markmail.org/message/ne6ucmnfqhkddnhu
> > FS and testplan:
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39620237
> > pull request: https://github.com/apache/cloudstack/pull/199
> >
> > Thanks,
> >
> > ~Rajani
>
>
>
> --
> Daan
>

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/199#discussion_r29309160
  
--- Diff: 
engine/storage/image/src/org/apache/cloudstack/storage/image/store/TemplateObject.java
 ---
@@ -28,7 +28,6 @@
 import 
org.apache.cloudstack.engine.subsystem.api.storage.DataObjectInStore;
 import org.apache.cloudstack.engine.subsystem.api.storage.DataStore;
 import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine;
-import 
org.apache.cloudstack.engine.subsystem.api.storage.ObjectInDataStoreStateMachine.Event;
--- End diff --

This is required for disambiguation. There are multiple Event objects. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Jenkins build is still unstable: simulator-singlerun #1158

[jenkins]

See 

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/199#issuecomment-97306176
  
closing this. created a new one #206


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

Github user karuturi closed the pull request at:

https://github.com/apache/cloudstack/pull/199


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [MERGE] Browser based template or volume ...

[karuturi]

GitHub user karuturi opened a pull request:

https://github.com/apache/cloudstack/pull/206

[MERGE] Browser based template or volume upload (resolved conflicts with 
master)

Proposal discussion: http://markmail.org/message/ne6ucmnfqhkddnhu
FS and testplan: 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39620237

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/cloudstack volume-upload-master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/206.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #206


commit 3da3d7418e9095f52b7a38dedb29d74adfcb0690
Author: Rajani Karuturi 
Date:   2014-11-19T12:23:14Z

volume upload: PSK exchange between managemnet server and SSVM

generated a key during management server start and saved it in
configurationt table

commit d2ef7295f90ea52788da0d99306bbcf84555cc5b
Author: Rajani Karuturi 
Date:   2014-11-28T11:10:20Z

volume upload: sending the preshared key to ssvm

sending the key to ssvm in the secondary storage setup command
saving it in a file on ssvm

commit b6c86bdb75143071c0f25e6cf9ca80a65ee63fa8
Author: Rajani Karuturi 
Date:   2014-11-28T11:31:16Z

changed commons-io version to the latest stable 2.4

also updated version numbers in all the poms its used.

commit b963bb1e6d6b49d585a7937071c5b2eb8371ba11
Author: Rajani Karuturi 
Date:   2014-12-02T06:45:42Z

volume upload: added getUploadParamsForVolume and 
getUploadParamsForTemplate api

commit 7e030ee72dd208bc50d5cf39a19c302ce0aee63d
Author: Rajani Karuturi 
Date:   2014-12-16T06:22:09Z

volume upload: persisting the template metadata

on calling GetUploadParamsForTemplate, persisting the metadata to db
validating the account limits and incrementing the appropriate limits
encoded the metadata on management server using preshared key

commit f70a2a1486e63e8860c163e569a524dd249dc048
Author: Rajani Karuturi 
Date:   2014-12-16T07:18:37Z

volume upload: renamed command classes to follow the naming convention

commit 36c0c38ab8294a222b25f6d7f6e5c8e80cc3aec2
Author: Rajani Karuturi 
Date:   2014-12-16T10:11:27Z

volume upload: added the url validation check when url is not null

commit 9bb6cf845284deaabb5e2ea8896cbb10b5935513
Author: Rajani Karuturi 
Date:   2014-12-18T12:20:51Z

volume upload: persisting the volume metadata

on calling GetUploadParamsForVolume, persisting the metadata to db
validating the account limits and incrementing the appropriate limits
encoded the metadata on management server using preshared key

commit 3e594c4e4f91271e4bfe60497163c62cfa466a83
Author: Rajani Karuturi 
Date:   2014-12-19T07:14:56Z

volume upload: removed unused variables

commit 42fdc343f593acc1998e44c65dc650cb0855f9c7
Author: Rajani Karuturi 
Date:   2015-01-06T05:37:10Z

volume upload: starting NIO server on SSVM

commit 2a4ca1b9c70556edb93492165fcf6eff4d7b13dc
Author: Rajani Karuturi 
Date:   2015-01-06T07:04:46Z

volume upload: fixed null in api response

commit 2c169bc02d3136ec9bb80bc8249d9209fceb3ab2
Author: Rajani Karuturi 
Date:   2015-01-09T03:46:00Z

volume-upload added a upload url redirect in apache conf

rewrite engine is on only in the case fo SSVM

commit 1ae34d98d49e232df276593b04f6563d1711b229
Author: Rajani Karuturi 
Date:   2015-01-13T05:11:39Z

volume upload: fixed circular reference error while generating json

commit 631e6e0088bea34031dcd5daf5bd27eafa99b3f9
Author: Rajani Karuturi 
Date:   2015-01-13T05:13:21Z

volume upload: doing https redirect as NioServer handles only https

commit c2cf2503c190fa4472a49a561fd529f5b48e278f
Author: Rajani Karuturi 
Date:   2015-01-13T06:07:22Z

volume upload: persisting the PSK only when its not present

commit 627f5a62dc71d7cfda53fa2b6bc4852a312aee02
Author: Koushik Das 
Date:   2015-01-14T04:49:12Z

volume upload: management server polling and upload status from agent
MS polling logic to query status for volumes that are uploaded

commit f243ae135b802d09077dde7bf20256f28c9e6287
Author: Brian Federle 
Date:   2015-01-14T19:26:38Z

Add front-end file uploader

commit 0eee9e8138092ed10ce298e763092367b7f9edd5
Author: Rajani Karuturi 
Date:   2015-01-16T06:52:35Z

volume upload: removed the transition from IN-PROGRESS to ABONDONED

incase of timeout it moved to error state. ABONDONED state is only when
the user hasnt initiated the post request in the specified time

commit 1f1c96d2eea88340c25bfacbab09d613c835a12c
Author: Koushik Das 
Date:   2015-01-16T09:58:17Z

volume upload: management server polling and upload status from agent
- Added config parameters for upload monitoring interval and operation 
timeout
- Some updates to the