date:20170124

[GitHub] cloudstack issue #1912: CLOUDSTACK-9749: Disable password service on ilb sys...

2017-01-24 Thread krissterckx

Github user krissterckx commented on the issue:

https://github.com/apache/cloudstack/pull/1912
  
LGTM


---
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 #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

2017-01-24 Thread ustcweizhou

GitHub user ustcweizhou opened a pull request:

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

CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.04 and support 
tomcat6/tomcat7

Changes
(1) seperate debian/control and debian/rules for Ubuntu 12.04/16.04
(2) add python-setuptools in Build-Depends
(3) seperate cloudstack-management.service and 
cloudstack-management.default for CentOS7 and Ubuntu 16.04
(4) add server7-ssl.xml and server7-nonssl.xml in management installation
(5) link /usr/share/cloudstack-management/lib and 
/usr/share/cloudstack-management/bin to correct path (tomcat6 or tomcat7)
(6) link /etc/cloudstack/management/server.xml to correct file path 
(server-nonssl.xml or server7-nonssl.xml)
(7) remove *.zip from .gitignore to avoid build error caused by missing 
/vhds/test.vhd.zip

Instruction
(1) build packages on Ubuntu 12.04/16.04: packaging/build_deb.sh
Output on Ubuntu 12.04: 
cloudstack-management_4.9.3.0-SNAPSHOT~precise_all.deb
Output on Ubuntu 16.04: 
cloudstack-management_4.9.3.0-SNAPSHOT~xenial_all.deb
(2) setup tomcat6/tomcat7 on management server: cloudstack-setup-management 
--tomcat7

Already tested on Ubuntu 12.04 and Ubuntu 16.04, upgraded from 4.7.1 to 
4.9.3.0-SNAPSHOT

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

$ git pull https://github.com/ustcweizhou/cloudstack 4.9-systemd-tomcat7

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

https://github.com/apache/cloudstack/pull/1916.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 #1916


commit fba99e534fcc967bf32461b08f1ccd9d91db8201
Author: Wei Zhou 
Date:   2017-01-24T09:34:21Z

CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.04 and support 
tomcat6/tomcat7

Changes
(1) seperate debian/control and debian/rules for Ubuntu 12.04/16.04
(2) add python-setuptools in Build-Depends
(3) seperate cloudstack-management.service and 
cloudstack-management.default for CentOS7 and Ubuntu 16.04
(4) add server7-ssl.xml and server7-nonssl.xml in management installation
(5) link /usr/share/cloudstack-management/lib and 
/usr/share/cloudstack-management/bin to correct path (tomcat6 or tomcat7)
(6) link /etc/cloudstack/management/server.xml to correct file path 
(server-nonssl.xml or server7-nonssl.xml)
(7) remove *.zip from .gitignore to avoid build error caused by missing 
/vhds/test.vhd.zip

Instruction
(1) build packages on Ubuntu 12.04/16.04: packaging/build_deb.sh
Output on Ubuntu 12.04: 
cloudstack-management_4.9.3.0-SNAPSHOT~precise_all.deb
Output on Ubuntu 16.04: 
cloudstack-management_4.9.3.0-SNAPSHOT~xenial_all.deb
(2) setup tomcat6/tomcat7 on management server: cloudstack-setup-management 
--tomcat7

Already tested on Ubuntu 12.04 and Ubuntu 16.04, upgraded from 4.7.1 to 
4.9.3.0-SNAPSHOT




---
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 issue #1040: CLOUDSTACK-9040: Use Tomcat6 for Debian packages.

2017-01-24 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1040
  
@JamesMcTavish I just created a PR for tomcat7/ubuntu 16.04 support. #1916
You can download the patch, apply it and build the packages by yourself.
https://github.com/apache/cloudstack/pull/1916.patch


---
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 issue #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.0...

2017-01-24 Thread wido

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1916
  
Why the ubuntu12 control file? Just to keep Ubuntu 12.04 support in there 
for CloudStack Management servers?

Since that would mean you'd have to rename files when building DEB packages 
for older distributions.


---
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 issue #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.0...

2017-01-24 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1916
  
@wido We will use packaging/build_deb.sh to build packages. It will get the 
os version, then copy corresponding files (debian control/rules) according to 
os version  , add os version (eg, precise/xenial) to tags .
This patch is for LTS 4.9 branch. We have 4.9.2 for Ubuntu 16.04 but it 
does not work with tomcat7. On the other hand, we do not provide packages for 
ubuntu 12.04/tomcat6. This patch will make them work well.
For 4.10/master, we can remove the files for ubuntu 12.04 if we decide to 
not support it anymore.



---
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: Adding VirtIO SCSI to KVM hypervisors

2017-01-24 Thread Syed Ahmed

To maintain backward compatibility we would have to add a config option
here unfortunately. I do like the idea however. We can make the default
VirtIO ISCSI and keep the VirtIO-blk as an alternative for existing
installations.

On Mon, Jan 23, 2017 at 8:05 AM, Wido den Hollander  wrote:

>
> > Op 21 januari 2017 om 23:50 schreef Wido den Hollander :
> >
> >
> >
> >
> > > Op 21 jan. 2017 om 22:59 heeft Syed Ahmed  het
> volgende geschreven:
> > >
> > > Exposing this via an API would be tricky but it can definitely be
> added as
> > > a cluster-wide or a global setting in my opinion. By enabling that,
> all the
> > > instances would be using VirtIO SCSI. Is there a reason you'd want some
> > > instances to use VirtIIO and others to use VirtIO SCSI?
> > >
> >
> > Even a global setting would be a bit of work and hacky as well.
> >
> > I do not see any reason to keep VirtIO, it os just that devices will be
> named sdX instead of vdX in the guest.
>
> To add, the Qemu wiki [0] says:
>
> "A virtio storage interface for efficient I/O that overcomes virtio-blk
> limitations and supports advanced SCSI hardware."
>
> At OpenStack [1] they also say:
>
> "It has been designed to replace virtio-blk, increase it's performance and
> improve scalability."
>
> So it seems that VirtIO is there to be removed. I'd say switch to VirtIO
> SCSI at version 5.X? :)
>
> Wido
>
> [0]: http://wiki.qemu.org/Features/VirtioSCSI
> [1]: https://wiki.openstack.org/wiki/LibvirtVirtioScsi
>
> >
> > That might break existing Instances when not using labels or UUIDs in
> the Instance when mounting.
> >
> > Wido
> >
> > >
> > >> On Sat, Jan 21, 2017 at 4:22 PM, Simon Weller 
> wrote:
> > >>
> > >> For the record, we've been looking into this as well.
> > >> Has anyone tried it with Windows VMs before? The standard virtio
> driver
> > >> doesn't support spanned disks and that's something we'd really like to
> > >> enable for our customers.
> > >>
> > >>
> > >>
> > >> Simon Weller/615-312-6068 <(615)%20312-6068>
> > >>
> > >>
> > >> -Original Message-
> > >> *From:* Wido den Hollander [w...@widodh.nl]
> > >> *Received:* Saturday, 21 Jan 2017, 2:56PM
> > >> *To:* Syed Ahmed [sah...@cloudops.com]; dev@cloudstack.apache.org [
> > >> dev@cloudstack.apache.org]
> > >> *Subject:* Re: Adding VirtIO SCSI to KVM hypervisors
> > >>
> > >>
> > >>> Op 21 januari 2017 om 16:15 schreef Syed Ahmed  >:
> > >>>
> > >>>
> > >>> Wido,
> > >>>
> > >>> Were you thinking of adding this as a global setting? I can see why
> it
> > >> will
> > >>> be useful. I'm happy to review any ideas you might have around this.
> > >>>
> > >>
> > >> Well, not really. We don't have any structure for this in place right
> now
> > >> to define what type of driver/disk we present to a guest.
> > >>
> > >> See my answer below.
> > >>
> > >>> Thanks,
> > >>> -Syed
> > >>> On Sat, Jan 21, 2017 at 04:46 Laszlo Hornyak <
> laszlo.horn...@gmail.com>
> > >>> wrote:
> > >>>
> >  Hi Wido,
> > 
> >  If I understand correctly from the documentation and your examples,
> > >> virtio
> >  provides virtio interface to the guest while virtio-scsi provides
> scsi
> >  interface, therefore an IaaS service should not replace it without
> user
> >  request / approval. It would be probably better to let the user set
> > >> what
> >  kind of IO interface the VM needs.
> > 
> > >>
> > >> You'd say, but we already do those. Some Operating Systems get a IDE
> disk,
> > >> others a SCSI disk and when Linux guest support it according to our
> > >> database we use VirtIO.
> > >>
> > >> CloudStack has no way of telling how to present a volume to a guest. I
> > >> think it would be a bit to much to just make that configurable. That
> would
> > >> mean extra database entries, API calls. A bit overkill imho in this
> case.
> > >>
> > >> VirtIO SCSI is supported by all Linux distributions for a very long
> time.
> > >>
> > >> Wido
> > >>
> >  Best regards,
> >  Laszlo
> > 
> >  On Fri, Jan 20, 2017 at 10:21 PM, Wido den Hollander <
> w...@widodh.nl>
> >  wrote:
> > 
> > > Hi,
> > >
> > > VirtIO SCSI [0] has been supported a while now by Linux and all
> > >> kernels,
> > > but inside CloudStack we are not using it. There is a issue for
> this
> > >> [1].
> > >
> > > It would bring more (theoretical) performance to VMs, but one of
> the
> > > motivators (for me) is that we can support TRIM/DISCARD [2].
> > >
> > > This would allow for RBD images on Ceph to shrink, but it can also
> > >> give
> > > back free space on QCOW2 images if quests run fstrim. Something all
> >  modern
> > > distributions all do weekly in a CRON.
> > >
> > > Now, it is simple to swap VirtIO for VirtIO SCSI. This would
> however
> > >> mean
> > > that disks inside VMs are then called /dev/sdX instead of /dev/vdX.
> > >
> > > For GRUB and such this is no problems. This usually work on UUIDs
> > >> and/or
> > > labels

[GitHub] cloudstack issue #1833: BUG-ID:CLOUDSTACK-9678

2017-01-24 Thread serg38

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1833
  
@pdumbre I confirm your observation. LGTM on code review.


---
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 #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

2017-01-24 Thread wido

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

https://github.com/apache/cloudstack/pull/1916#discussion_r97613420
  
--- Diff: debian/rules ---
@@ -149,7 +150,7 @@ override_dh_installinit:
dh_installinit -pcloudstack-management -pcloudstack-agent 
-pcloudstack-usage --onlyscripts --no-start
 
 override_dh_systemd_enable:
-   dh_systemd_enable -pcloudstack-agent -pcloudstack-usage
+   dh_systemd_enable -pcloudstack-management -pcloudstack-agent 
-pcloudstack-usage
--- End diff --

Shouldn't we somehow clean up any left behind script in /etc/init.d of the 
management server?


---
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 #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

2017-01-24 Thread wido

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

https://github.com/apache/cloudstack/pull/1916#discussion_r97613140
  
--- Diff: debian/cloudstack-management.postinst ---
@@ -60,7 +60,26 @@ if [ "$1" = configure ]; then
 
 chmod 0640 ${CONFDIR}/${DBPROPS}
 chgrp cloud ${CONFDIR}/${DBPROPS}
-invoke-rc.d tomcat6 stop || true
+
+if [ -d "/usr/share/tomcat7" ]; then
+rm -f /usr/share/cloudstack-management/bin
+rm -f /usr/share/cloudstack-management/lib
+ln -s /usr/share/tomcat7/bin /usr/share/cloudstack-management/bin
+ln -s /usr/share/tomcat7/lib /usr/share/cloudstack-management/lib
+invoke-rc.d tomcat7 stop || true
+if [ ! -f "/etc/cloudstack/management/server.xml" ]; then
+ln -s /etc/cloudstack/management/server7-nonssl.xml 
/etc/cloudstack/management/server.xml
+fi
+elif [ -d "/usr/share/tomcat6" ]; then
+rm -f /usr/share/cloudstack-management/bin
+rm -f /usr/share/cloudstack-management/lib
+ln -s /usr/share/tomcat6/bin /usr/share/cloudstack-management/bin
+ln -s /usr/share/tomcat6/lib /usr/share/cloudstack-management/lib
+invoke-rc.d tomcat6 stop || true
+if [ ! -f "/etc/cloudstack/management/server.xml" ]; then
+ln -s /etc/cloudstack/management/server-nonssl.xml 
/etc/cloudstack/management/server.xml
+fi
+fi
--- End diff --

Not sure if we this is the best way. Usually creating directories and 
moving symlinks is not the way to go in postinst files.

When cleaning packages or upgrading this might break things. Can you think 
of a different way?


---
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 issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread nathanejohnson

Github user nathanejohnson commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@ustcweizhou @kiwiflyer I was finally able to get an environment to run 
tests.  So far I have reworked smoke/test_vm_snapshots.py with @kiwiflyer so 
that it handles the chnages from this PR for KVM, and the tests were successful:

@Desc: Test that Volume snapshot for root volume is not allowed ... SKIP: 
Skipping test because unsupportedhypervisor KVM
Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
Status : SUCCESS ===
ok
Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
Status : SUCCESS ===
ok
Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
Status : SUCCESS ===
ok

--
Ran 4 tests in 564.793s

OK (SKIP=1)

@ustcweizhou I committed those to a branch we forked from your vm-snapshot 
branch, and then we rebased it off of master.  Would you like me to open a PR 
against your fork / 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.
---

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@nathanejohnson do you mean the commit 7a2a1c1 ? I can add it into this PR 
so you do not need to open a new PR.



---
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 issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread leprechau

Github user leprechau commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@ustcweizhou Nathan's work can be found in the `vm-snapshot` branch of our 
fork here: https://github.com/myENA/cloudstack/commits/vm-snapshot


---
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 #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

2017-01-24 Thread ustcweizhou

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

https://github.com/apache/cloudstack/pull/1916#discussion_r97643865
  
--- Diff: debian/rules ---
@@ -149,7 +150,7 @@ override_dh_installinit:
dh_installinit -pcloudstack-management -pcloudstack-agent 
-pcloudstack-usage --onlyscripts --no-start
 
 override_dh_systemd_enable:
-   dh_systemd_enable -pcloudstack-agent -pcloudstack-usage
+   dh_systemd_enable -pcloudstack-management -pcloudstack-agent 
-pcloudstack-usage
--- End diff --

@wido we should if we do not support ubuntu 12.04 anymore. I prefer to 
remove it in 4.10. I can create another PR for it. This PR is only for 4.9 
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.
---

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread nathanejohnson

Github user nathanejohnson commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@ustcweizhou I just now squashed the commits, but the branch @leprechau 
mentioned above is the branch I was working on that incorporates that commit 
plus a few others.

Thanks


---
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 #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

2017-01-24 Thread ustcweizhou

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

https://github.com/apache/cloudstack/pull/1916#discussion_r97645697
  
--- Diff: debian/cloudstack-management.postinst ---
@@ -60,7 +60,26 @@ if [ "$1" = configure ]; then
 
 chmod 0640 ${CONFDIR}/${DBPROPS}
 chgrp cloud ${CONFDIR}/${DBPROPS}
-invoke-rc.d tomcat6 stop || true
+
+if [ -d "/usr/share/tomcat7" ]; then
+rm -f /usr/share/cloudstack-management/bin
+rm -f /usr/share/cloudstack-management/lib
+ln -s /usr/share/tomcat7/bin /usr/share/cloudstack-management/bin
+ln -s /usr/share/tomcat7/lib /usr/share/cloudstack-management/lib
+invoke-rc.d tomcat7 stop || true
+if [ ! -f "/etc/cloudstack/management/server.xml" ]; then
+ln -s /etc/cloudstack/management/server7-nonssl.xml 
/etc/cloudstack/management/server.xml
+fi
+elif [ -d "/usr/share/tomcat6" ]; then
+rm -f /usr/share/cloudstack-management/bin
+rm -f /usr/share/cloudstack-management/lib
+ln -s /usr/share/tomcat6/bin /usr/share/cloudstack-management/bin
+ln -s /usr/share/tomcat6/lib /usr/share/cloudstack-management/lib
+invoke-rc.d tomcat6 stop || true
+if [ ! -f "/etc/cloudstack/management/server.xml" ]; then
+ln -s /etc/cloudstack/management/server-nonssl.xml 
/etc/cloudstack/management/server.xml
+fi
+fi
--- End diff --

@wido I was thinking of other ways but could not find. Do you have any idea?
We can remove this change and ask users to execute 
"cloudstack-setup-management --tomcat7" after each upgrade. It seems not wise.

I have tested the upgrade from 4.7.1 to 4.9.3.0-SNAPSHOT on ubuntu 12.04 
and 16.04 without any issue.
I did not test the os upgrade or tomcat upgrade.


---
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 issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread nathanejohnson

Github user nathanejohnson commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@ustcweizhou for what it's worth, our branch / fork has all changes from 
master incorporated


---
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 issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread ustcweizhou

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
@nathanejohnson I rebased my branch with latest master, and apply your 
commit. 
now this PR should have same code with vm-snapshot branch under your 
account.


---
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 Collab in Miami

2017-01-24 Thread Will Stevens

Hello Everyone,
It is that time of the year again.  We are into the thick of it planning
the next CloudStack Collaboration Conference (CCC).

We are happy to announce that the first CloudStack Collab of 2017 will be
taking place on May 16-18 in Miami.  CloudStack has partnered with
ApacheCon to bring you a great event.

More information about the conference is available here:
http://us.cloudstackcollab.org/

Here are some of the important details:

- The *speaker submission deadline is Feb 11th*, so get your talks in
early.  Details here: http://us.cloudstackcollab.org/#get-involved

- Registration will be taken care of by ApacheCon.  Details here:
http://us.cloudstackcollab.org/#attend

- Travel information and details about the venue can be found here:
http://us.cloudstackcollab.org/#location

- Consider sponsoring the event to make it even better. More info here:
http://us.cloudstackcollab.org/#sponsors

If you have any questions, please respond to this email and I will make
sure your questions are answered.

Looking forward to seeing you all in Miami...

Cheers,

Will

Re: CloudStack Collab in Miami

2017-01-24 Thread Rafael Weingärtner

I would like to add that speakers of CCC have free access to ApacheCon.
This represents big savings (US$600 for early registrations). You can use
that money to extend your stay for a weekend and enjoy the sunshine of
Miami ;)

Submit a proposal of presentation and join us in Miami. You can show the
community exciting hacks you have done with Apache CloudStack; discuss new
features and those little bugs that keep coming up from time to time. It is
a great opportunity to put a face on names that you just know from our
mailing lists.

I would also like to highlight that ApacheCon creates a unique opportunity
for you to meet great people from all around the world. You will find
people from most Apache projects (our little community included).

Looking forward to seeing you all in Miami
Cheers

On Tue, Jan 24, 2017 at 4:27 PM, Will Stevens  wrote:

> Hello Everyone,
> It is that time of the year again.  We are into the thick of it planning
> the next CloudStack Collaboration Conference (CCC).
>
> We are happy to announce that the first CloudStack Collab of 2017 will be
> taking place on May 16-18 in Miami.  CloudStack has partnered with
> ApacheCon to bring you a great event.
>
> More information about the conference is available here:
> http://us.cloudstackcollab.org/
>
> Here are some of the important details:
>
> - The *speaker submission deadline is Feb 11th*, so get your talks in
> early.  Details here: http://us.cloudstackcollab.org/#get-involved
>
> - Registration will be taken care of by ApacheCon.  Details here:
> http://us.cloudstackcollab.org/#attend
>
> - Travel information and details about the venue can be found here:
> http://us.cloudstackcollab.org/#location
>
> - Consider sponsoring the event to make it even better. More info here:
> http://us.cloudstackcollab.org/#sponsors
>
> If you have any questions, please respond to this email and I will make
> sure your questions are answered.
>
> Looking forward to seeing you all in Miami...
>
> Cheers,
>
> Will
>

-- 
Rafael Weingärtner

Re: RM for 4.10/master

2017-01-24 Thread Rajani Karuturi

We are facing some issues with our intenral CI post java8
changes. It might take a couple of days to resolve.

I will start merging the PRs once that is done. Meanwhile, I will
start reviewing the PRs.

I am tentatively looking at creating RC at the end of Feb.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On January 19, 2017 at 8:34 PM, Simon Weller (swel...@ena.com)
wrote:

Great, thanks Rajani!


From: Rajani Karuturi 
Sent: Thursday, January 19, 2017 1:15 AM
To: dev@cloudstack.apache.org
Subject: Re: RM for 4.10/master

Yes. thats true. Offlate I was busy with $dayjob activities and
wasnt able to give it enough time.

Starting next week, I will start working on it.

@Rohit, Is it possible to give me access to run CI?

~ Rajani

http://cloudplatform.accelerite.com/

On January 18, 2017 at 11:13 PM, Simon Weller (swel...@ena.com)
wrote:

I think Rajani had originally volunteered to be RM for 4.10 a
couple of months back.


From: Sergey Levitskiy 
Sent: Wednesday, January 18, 2017 11:34 AM
To: dev@cloudstack.apache.org
Subject: Re: RM for 4.10/master

There are many PR in the merge ready state or require
BlueOrangutan testing. Are there volunteers for 4.10 RM role?

On 1/16/17, 4:46 AM, "Rohit Yadav" 
wrote:

All,

I will be on holidays after 18th January and have other work
commitments, I won't be able to contribute much time on RM work.

Please feel free to take up RM responsibilities for 4.10
release, as per our schedule we wanted to freeze it by end of
this month. I can work with the new RM and help them use
@blueorangutan and Trillian for test related work.

Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
ShapeBlue - The CloudStack Company
www.shapeblue.com 
( http://www.shapeblue.com )
Introduction Upgrading CloudStack can sometimes be a little
daunting - but as the 5P's proverb goes - Proper Planning
Prevents Poor Performance.

53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue

[GitHub] cloudstack issue #1797: CLOUDSTACK-9630: Cannot use listNics API as advertis...

2017-01-24 Thread pdion891

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1797
  
as it been confirmed the the attribute `broadcasturi = vlan://743` is only 
visible as admin and not as user? because the example have 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 issue #1741: Updated StrongSwan VPN Implementation

2017-01-24 Thread blueorangutan

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
Trillian test result (tid-785)
Environment: kvm-centos7 (x1), Advanced Networking with Mgmt server 7
Total time taken: 34369 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1741-t785-kvm-centos7.zip
Intermitten failure detected: 
/marvin/tests/smoke/test_affinity_groups_projects.py
Intermitten failure detected: /marvin/tests/smoke/test_affinity_groups.py
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Test completed. 45 look ok, 4 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_01_vpc_site2site_vpn | `Failure` | 155.41 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | `Failure` | 220.58 | test_vpc_vpn.py
test_02_redundant_VPC_default_routes | `Failure` | 848.90 | 
test_vpc_redundant.py
test_04_rvpc_privategw_static_routes | `Failure` | 300.60 | 
test_privategw_acl.py
test_DeployVmAntiAffinityGroup | `Error` | 70.93 | test_affinity_groups.py
test_01_vpc_remote_access_vpn | Success | 61.06 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 272.13 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 455.18 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 480.53 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1387.47 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 527.99 | test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1268.53 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 156.69 | test_volumes.py
test_08_resize_volume | Success | 151.38 | test_volumes.py
test_07_resize_fail | Success | 156.50 | test_volumes.py
test_06_download_detached_volume | Success | 156.33 | test_volumes.py
test_05_detach_volume | Success | 145.76 | test_volumes.py
test_04_delete_attached_volume | Success | 146.24 | test_volumes.py
test_03_download_attached_volume | Success | 151.29 | test_volumes.py
test_02_attach_volume | Success | 89.09 | test_volumes.py
test_01_create_volume | Success | 620.84 | test_volumes.py
test_deploy_vm_multiple | Success | 252.72 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.71 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.17 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.85 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.87 | test_vm_life_cycle.py
test_02_start_vm | Success | 5.14 | test_vm_life_cycle.py
test_01_stop_vm | Success | 35.33 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 50.61 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.05 | test_templates.py
test_04_extract_template | Success | 5.15 | test_templates.py
test_03_delete_template | Success | 5.10 | test_templates.py
test_02_edit_template | Success | 90.10 | test_templates.py
test_01_create_template | Success | 30.36 | test_templates.py
test_10_destroy_cpvm | Success | 161.37 | test_ssvm.py
test_09_destroy_ssvm | Success | 133.46 | test_ssvm.py
test_08_reboot_cpvm | Success | 131.38 | test_ssvm.py
test_07_reboot_ssvm | Success | 103.38 | test_ssvm.py
test_06_stop_cpvm | Success | 131.48 | test_ssvm.py
test_05_stop_ssvm | Success | 163.31 | test_ssvm.py
test_04_cpvm_internals | Success | 0.96 | test_ssvm.py
test_03_ssvm_internals | Success | 2.88 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.22 | test_snapshots.py
test_04_change_offering_small | Success | 204.56 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
test_01_create_service_offering | Success | 0.11 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.14 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.19 | test_secondary_storage.py
test_09_reboot_router | Success | 35.30 | test_routers.py
test_08_start_router |

Re: RM for 4.10/master

2017-01-24 Thread Tutkowski, Mike

Hi Rajani,

I’m not sure when you’ll be building your list of PRs to put into 4.10, but 
could you consider this one (it addresses an issue that went into 4.10 with PR 
1600)?

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

Thanks!
Mike

On 1/24/17, 4:49 PM, "Rajani Karuturi"  wrote:

We are facing some issues with our intenral CI post java8
changes. It might take a couple of days to resolve.

I will start merging the PRs once that is done. Meanwhile, I will
start reviewing the PRs.

I am tentatively looking at creating RC at the end of Feb.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On January 19, 2017 at 8:34 PM, Simon Weller (swel...@ena.com)
wrote:

Great, thanks Rajani!


From: Rajani Karuturi 
Sent: Thursday, January 19, 2017 1:15 AM
To: dev@cloudstack.apache.org
Subject: Re: RM for 4.10/master

Yes. thats true. Offlate I was busy with $dayjob activities and
wasnt able to give it enough time.

Starting next week, I will start working on it.

@Rohit, Is it possible to give me access to run CI?

~ Rajani

http://cloudplatform.accelerite.com/

On January 18, 2017 at 11:13 PM, Simon Weller (swel...@ena.com)
wrote:

I think Rajani had originally volunteered to be RM for 4.10 a
couple of months back.


From: Sergey Levitskiy 
Sent: Wednesday, January 18, 2017 11:34 AM
To: dev@cloudstack.apache.org
Subject: Re: RM for 4.10/master

There are many PR in the merge ready state or require
BlueOrangutan testing. Are there volunteers for 4.10 RM role?

On 1/16/17, 4:46 AM, "Rohit Yadav" 
wrote:

All,

I will be on holidays after 18th January and have other work
commitments, I won't be able to contribute much time on RM work.

Please feel free to take up RM responsibilities for 4.10
release, as per our schedule we wanted to freeze it by end of
this month. I can work with the new RM and help them use
@blueorangutan and Trillian for test related work.

Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
ShapeBlue - The CloudStack Company
www.shapeblue.com 
( http://www.shapeblue.com )
Introduction Upgrading CloudStack can sometimes be a little
daunting - but as the 5P's proverb goes - Proper Planning
Prevents Poor Performance.

53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

2017-01-24 Thread kiwiflyer

Github user kiwiflyer commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
Great job all. I think this one is ready.
@ustcweizhou @nathanejohnson 


---
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: Adding VirtIO SCSI to KVM hypervisors

2017-01-24 Thread Simon Weller

Maybe this is a good opportunity to discuss modernizing the OS selections so 
that drivers (and other features) could be selectable per OS.


Thoughts?



From: Syed Ahmed 
Sent: Tuesday, January 24, 2017 10:46 AM
To: dev@cloudstack.apache.org
Cc: Simon Weller
Subject: Re: Adding VirtIO SCSI to KVM hypervisors

To maintain backward compatibility we would have to add a config option here 
unfortunately. I do like the idea however. We can make the default VirtIO ISCSI 
and keep the VirtIO-blk as an alternative for existing installations.

On Mon, Jan 23, 2017 at 8:05 AM, Wido den Hollander 
mailto:w...@widodh.nl>> wrote:

> Op 21 januari 2017 om 23:50 schreef Wido den Hollander 
> mailto:w...@widodh.nl>>:
>
>
>
>
> > Op 21 jan. 2017 om 22:59 heeft Syed Ahmed 
> > mailto:sah...@cloudops.com>> het volgende geschreven:
> >
> > Exposing this via an API would be tricky but it can definitely be added as
> > a cluster-wide or a global setting in my opinion. By enabling that, all the
> > instances would be using VirtIO SCSI. Is there a reason you'd want some
> > instances to use VirtIIO and others to use VirtIO SCSI?
> >
>
> Even a global setting would be a bit of work and hacky as well.
>
> I do not see any reason to keep VirtIO, it os just that devices will be named 
> sdX instead of vdX in the guest.

To add, the Qemu wiki [0] says:

"A virtio storage interface for efficient I/O that overcomes virtio-blk 
limitations and supports advanced SCSI hardware."

At OpenStack [1] they also say:

"It has been designed to replace virtio-blk, increase it's performance and 
improve scalability."

So it seems that VirtIO is there to be removed. I'd say switch to VirtIO SCSI 
at version 5.X? :)

Wido

[0]: http://wiki.qemu.org/Features/VirtioSCSI
[1]: https://wiki.openstack.org/wiki/LibvirtVirtioScsi

>
> That might break existing Instances when not using labels or UUIDs in the 
> Instance when mounting.
>
> Wido
>
> >
> >> On Sat, Jan 21, 2017 at 4:22 PM, Simon Weller 
> >> mailto:swel...@ena.com>> wrote:
> >>
> >> For the record, we've been looking into this as well.
> >> Has anyone tried it with Windows VMs before? The standard virtio driver
> >> doesn't support spanned disks and that's something we'd really like to
> >> enable for our customers.
> >>
> >>
> >>
> >> Simon Weller/615-312-6068 <(615)%20312-6068>
> >>
> >>
> >> -Original Message-
> >> *From:* Wido den Hollander [w...@widodh.nl]
> >> *Received:* Saturday, 21 Jan 2017, 2:56PM
> >> *To:* Syed Ahmed [sah...@cloudops.com]; 
> >> dev@cloudstack.apache.org [
> >> dev@cloudstack.apache.org]
> >> *Subject:* Re: Adding VirtIO SCSI to KVM hypervisors
> >>
> >>
> >>> Op 21 januari 2017 om 16:15 schreef Syed Ahmed 
> >>> mailto:sah...@cloudops.com>>:
> >>>
> >>>
> >>> Wido,
> >>>
> >>> Were you thinking of adding this as a global setting? I can see why it
> >> will
> >>> be useful. I'm happy to review any ideas you might have around this.
> >>>
> >>
> >> Well, not really. We don't have any structure for this in place right now
> >> to define what type of driver/disk we present to a guest.
> >>
> >> See my answer below.
> >>
> >>> Thanks,
> >>> -Syed
> >>> On Sat, Jan 21, 2017 at 04:46 Laszlo Hornyak 
> >>> mailto:laszlo.horn...@gmail.com>>
> >>> wrote:
> >>>
>  Hi Wido,
> 
>  If I understand correctly from the documentation and your examples,
> >> virtio
>  provides virtio interface to the guest while virtio-scsi provides scsi
>  interface, therefore an IaaS service should not replace it without user
>  request / approval. It would be probably better to let the user set
> >> what
>  kind of IO interface the VM needs.
> 
> >>
> >> You'd say, but we already do those. Some Operating Systems get a IDE disk,
> >> others a SCSI disk and when Linux guest support it according to our
> >> database we use VirtIO.
> >>
> >> CloudStack has no way of telling how to present a volume to a guest. I
> >> think it would be a bit to much to just make that configurable. That would
> >> mean extra database entries, API calls. A bit overkill imho in this case.
> >>
> >> VirtIO SCSI is supported by all Linux distributions for a very long time.
> >>
> >> Wido
> >>
>  Best regards,
>  Laszlo
> 
>  On Fri, Jan 20, 2017 at 10:21 PM, Wido den Hollander 
>  mailto:w...@widodh.nl>>
>  wrote:
> 
> > Hi,
> >
> > VirtIO SCSI [0] has been supported a while now by Linux and all
> >> kernels,
> > but inside CloudStack we are not using it. There is a issue for this
> >> [1].
> >
> > It would bring more (theoretical) performance to VMs, but one of the
> > motivators (for me) is that we can support TRIM/DISCARD [2].
> >
> > This would allow for RBD images on Ceph to shrink, but it can also
> >> give
> > back free space on QCOW2 images if quests run fstrim.

[GitHub] cloudstack issue #1797: CLOUDSTACK-9630: Cannot use listNics API as advertis...

2017-01-24 Thread sudhansu7

Github user sudhansu7 commented on the issue:

https://github.com/apache/cloudstack/pull/1797
  
@pdion891 
The first listNic example is incorrect code. Which has been fixed in this 
PR.  You can use listVirtualMachine command to see the nic response. 

As per code there is no restriction on broadcasturi. If broadcasturi is not 
null then it will part of vm response. 
So the ListNic should also behave the same way.

'''
if (details.contains(VMDetails.all) || details.contains(VMDetails.nics)) {
long nic_id = userVm.getNicId();
if (nic_id > 0) {
NicResponse nicResponse = new NicResponse();
nicResponse.setId(userVm.getNicUuid());
nicResponse.setIpaddress(userVm.getIpAddress());
nicResponse.setGateway(userVm.getGateway());
nicResponse.setNetmask(userVm.getNetmask());
nicResponse.setNetworkid(userVm.getNetworkUuid());
nicResponse.setNetworkName(userVm.getNetworkName());
nicResponse.setMacAddress(userVm.getMacAddress());
nicResponse.setIp6Address(userVm.getIp6Address());
nicResponse.setIp6Gateway(userVm.getIp6Gateway());
nicResponse.setIp6Cidr(userVm.getIp6Cidr());
if (userVm.getBroadcastUri() != null) {

nicResponse.setBroadcastUri(userVm.getBroadcastUri().toString());
}
if (userVm.getIsolationUri() != null) {

nicResponse.setIsolationUri(userVm.getIsolationUri().toString());
}
if (userVm.getTrafficType() != null) {

nicResponse.setTrafficType(userVm.getTrafficType().toString());
}
if (userVm.getGuestType() != null) {
nicResponse.setType(userVm.getGuestType().toString());
}
nicResponse.setIsDefault(userVm.isDefaultNic());
List secondaryIps = 
ApiDBUtils.findNicSecondaryIps(userVm.getNicId());
if (secondaryIps != null) {
List ipList = new 
ArrayList();
for (NicSecondaryIpVO ip : secondaryIps) {
NicSecondaryIpResponse ipRes = new 
NicSecondaryIpResponse();
ipRes.setId(ip.getUuid());
ipRes.setIpAddr(ip.getIp4Address());
ipList.add(ipRes);
}
nicResponse.setSecondaryIps(ipList);
}
nicResponse.setObjectName("nic");
userVmResponse.addNic(nicResponse);
}
}
'''
Is there any 


---
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 #1917: CLOUDSTACK-9756: Configure to ignore the ipas...

2017-01-24 Thread jayapalu

GitHub user jayapalu opened a pull request:

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

CLOUDSTACK-9756: Configure to  ignore the ipassoc failure


On failure of ip assoc in back end (In VR), added config option to ignore 
or not to ignore failure. Using this failures won't be ignored and ip address 
will not set to free in DB.

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

$ git pull https://github.com/Accelerite/cloudstack RvRipRel

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

https://github.com/apache/cloudstack/pull/1917.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 #1917


commit 66b0033cc9456dd875425387f92169dbdec005bf
Author: Jayapal 
Date:   2017-01-24T09:53:17Z

CLOUDSTACK-9756: Configure to  ignore the ipassoc failure




---
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: Adding VirtIO SCSI to KVM hypervisors

2017-01-24 Thread Wido den Hollander


> Op 25 januari 2017 om 4:44 schreef Simon Weller :
> 
> 
> Maybe this is a good opportunity to discuss modernizing the OS selections so 
> that drivers (and other features) could be selectable per OS.
> 

That seems like a good idea. If you select Ubuntu 16.04 or CentOS 7.3 then for 
example it will give you a VirtIO SCSI disk on KVM, anything previous to that 
will get VirtIO-blk.

Wido

> 
> Thoughts?
> 
> 
> 
> From: Syed Ahmed 
> Sent: Tuesday, January 24, 2017 10:46 AM
> To: dev@cloudstack.apache.org
> Cc: Simon Weller
> Subject: Re: Adding VirtIO SCSI to KVM hypervisors
> 
> To maintain backward compatibility we would have to add a config option here 
> unfortunately. I do like the idea however. We can make the default VirtIO 
> ISCSI and keep the VirtIO-blk as an alternative for existing installations.
> 
> On Mon, Jan 23, 2017 at 8:05 AM, Wido den Hollander 
> mailto:w...@widodh.nl>> wrote:
> 
> > Op 21 januari 2017 om 23:50 schreef Wido den Hollander 
> > mailto:w...@widodh.nl>>:
> >
> >
> >
> >
> > > Op 21 jan. 2017 om 22:59 heeft Syed Ahmed 
> > > mailto:sah...@cloudops.com>> het volgende geschreven:
> > >
> > > Exposing this via an API would be tricky but it can definitely be added as
> > > a cluster-wide or a global setting in my opinion. By enabling that, all 
> > > the
> > > instances would be using VirtIO SCSI. Is there a reason you'd want some
> > > instances to use VirtIIO and others to use VirtIO SCSI?
> > >
> >
> > Even a global setting would be a bit of work and hacky as well.
> >
> > I do not see any reason to keep VirtIO, it os just that devices will be 
> > named sdX instead of vdX in the guest.
> 
> To add, the Qemu wiki [0] says:
> 
> "A virtio storage interface for efficient I/O that overcomes virtio-blk 
> limitations and supports advanced SCSI hardware."
> 
> At OpenStack [1] they also say:
> 
> "It has been designed to replace virtio-blk, increase it's performance and 
> improve scalability."
> 
> So it seems that VirtIO is there to be removed. I'd say switch to VirtIO SCSI 
> at version 5.X? :)
> 
> Wido
> 
> [0]: http://wiki.qemu.org/Features/VirtioSCSI
> [1]: https://wiki.openstack.org/wiki/LibvirtVirtioScsi
> 
> >
> > That might break existing Instances when not using labels or UUIDs in the 
> > Instance when mounting.
> >
> > Wido
> >
> > >
> > >> On Sat, Jan 21, 2017 at 4:22 PM, Simon Weller 
> > >> mailto:swel...@ena.com>> wrote:
> > >>
> > >> For the record, we've been looking into this as well.
> > >> Has anyone tried it with Windows VMs before? The standard virtio driver
> > >> doesn't support spanned disks and that's something we'd really like to
> > >> enable for our customers.
> > >>
> > >>
> > >>
> > >> Simon Weller/615-312-6068 <(615)%20312-6068>
> > >>
> > >>
> > >> -Original Message-
> > >> *From:* Wido den Hollander [w...@widodh.nl]
> > >> *Received:* Saturday, 21 Jan 2017, 2:56PM
> > >> *To:* Syed Ahmed [sah...@cloudops.com]; 
> > >> dev@cloudstack.apache.org [
> > >> dev@cloudstack.apache.org]
> > >> *Subject:* Re: Adding VirtIO SCSI to KVM hypervisors
> > >>
> > >>
> > >>> Op 21 januari 2017 om 16:15 schreef Syed Ahmed 
> > >>> mailto:sah...@cloudops.com>>:
> > >>>
> > >>>
> > >>> Wido,
> > >>>
> > >>> Were you thinking of adding this as a global setting? I can see why it
> > >> will
> > >>> be useful. I'm happy to review any ideas you might have around this.
> > >>>
> > >>
> > >> Well, not really. We don't have any structure for this in place right now
> > >> to define what type of driver/disk we present to a guest.
> > >>
> > >> See my answer below.
> > >>
> > >>> Thanks,
> > >>> -Syed
> > >>> On Sat, Jan 21, 2017 at 04:46 Laszlo Hornyak 
> > >>> mailto:laszlo.horn...@gmail.com>>
> > >>> wrote:
> > >>>
> >  Hi Wido,
> > 
> >  If I understand correctly from the documentation and your examples,
> > >> virtio
> >  provides virtio interface to the guest while virtio-scsi provides scsi
> >  interface, therefore an IaaS service should not replace it without user
> >  request / approval. It would be probably better to let the user set
> > >> what
> >  kind of IO interface the VM needs.
> > 
> > >>
> > >> You'd say, but we already do those. Some Operating Systems get a IDE 
> > >> disk,
> > >> others a SCSI disk and when Linux guest support it according to our
> > >> database we use VirtIO.
> > >>
> > >> CloudStack has no way of telling how to present a volume to a guest. I
> > >> think it would be a bit to much to just make that configurable. That 
> > >> would
> > >> mean extra database entries, API calls. A bit overkill imho in this case.
> > >>
> > >> VirtIO SCSI is supported by all Linux distributions for a very long time.
> > >>
> > >> Wido
> > >>
> >  Best regards,
> >  Laszlo
> > 
> >  On Fri, Jan 20, 2017 at 10:21 PM, Wido den Hollander 
> >  m

[GitHub] cloudstack issue #1912: CLOUDSTACK-9749: Disable password service on ilb sys...

[GitHub] cloudstack pull request #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

[GitHub] cloudstack issue #1040: CLOUDSTACK-9040: Use Tomcat6 for Debian packages.

[GitHub] cloudstack issue #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.0...

[GitHub] cloudstack issue #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12.04/16.0...

Re: Adding VirtIO SCSI to KVM hypervisors

[GitHub] cloudstack issue #1833: BUG-ID:CLOUDSTACK-9678

[GitHub] cloudstack pull request #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

[GitHub] cloudstack pull request #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[GitHub] cloudstack pull request #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[GitHub] cloudstack pull request #1916: CLOUDSTACK-9462: Build packages on Ubuntu 12....

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

CloudStack Collab in Miami

Re: CloudStack Collab in Miami

Re: RM for 4.10/master

[GitHub] cloudstack issue #1797: CLOUDSTACK-9630: Cannot use listNics API as advertis...

[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

Re: RM for 4.10/master

[GitHub] cloudstack issue #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

Re: Adding VirtIO SCSI to KVM hypervisors

[GitHub] cloudstack issue #1797: CLOUDSTACK-9630: Cannot use listNics API as advertis...

[GitHub] cloudstack pull request #1917: CLOUDSTACK-9756: Configure to ignore the ipas...

Re: Adding VirtIO SCSI to KVM hypervisors

28 matches

Site Navigation

Mail list logo

Footer information