[GitHub] [cloudstack-documentation] davidjumani opened a new pull request #207: Updating image and docs wrt the new UI

[GitBox]

davidjumani opened a new pull request #207:
URL: https://github.com/apache/cloudstack-documentation/pull/207


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PROPOSAL] Force option and/or command to the detach ISO operation for running VMs

[Rohit Yadav]

+1 makes sense - good approach to maintain backward compatibility but have an 
option to force eject. Does kvm/xenserver/xcp also support force 
ejecting/detaching of ISOs like VMware?


Regards.


From: Harikrishna Patnala 
Sent: Monday, April 12, 2021 11:30
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

Yes, it's better to keep an optional flag in the API params to decide on force 
detach of ISO instead of hardcoding force in the final detach operation. Thats 
gives flexibility to users and also keeps backward compatibility.

+1

Regards,
Harikrishna

From: Pearl d'Silva 
Sent: Friday, April 9, 2021 6:27 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

I've seen this issue happen on VMware.
+1 on having a force option to the attach/detach iso operations, thus giving 
control to the users as opposed to hard-coding the answer in the code.

Regards,
Pearl

From: Nicolas Vazquez 
Sent: Tuesday, March 30, 2021 4:06 AM
To: us...@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

Hi Alireza,

Yes - I have seen the same. In my tests that VM question was the one with ID 
'msg.cdromdisconnect.locked' to which CloudStack always answered "no" to that 
question and there was no option to control which answer to send.

I also noticed that the answering that question is only handled in the Vmware 
codebase, but not on other hypervisors codebase.


Regards,

Nicolas Vazquez


From: Alireza Eskandari 
Sent: Monday, March 29, 2021 3:40 PM
To: us...@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

Hi Nicolas
AFAIK in these situations ESXi will raise a question about detaching iso
from VM.
I have faced with similar problem in this issue:
https://github.com/apache/cloudstack/issues/4808
I got the same error in vCenter. Before waiting for timeout, if you click
on the refresh button in the top right corner of the web gui, you can see
an unanswered question is raised for the VM.
Regards

On Mon, Mar 29, 2021 at 7:34 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> Hi all,
>
> I have observed a non-consistent issue on the detach ISO operation for
> running VMs. Some guest OS refuse to release an attached ISO even though
> the ISO is not mounted, making the detach ISO operation fail if the VM is
> running. For example, a CentOS 7 running VM on Vmware 6.5 fails to detach
> an ISO with error: 'Connection control operation failed for disk 'ide0:0'
> if the VM is running'. However, there is no issue if the VM is stopped.
>
> As a workaround executing an 'eject' command on the guest VM before the
> detach operation solves the problem. The detach ISO operation in CloudStack
> could be extended to support a 'force' option - which could perform a
> similar workaround when the VM is running.
>
> I would be interested to know if you have experimented similar issues on
> different hypervisors or could be some hypervisor specific version issue.
>
>
> Regards,
>
> Nicolas Vazquez
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

nicolas.vazq...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




pearl.dsi...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




harikrishna.patn...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: multiple SSH keys. Question to the dev community members

[Rohit Yadav]

Hi Bikram,

Thanks for starting the thread and welcome to the dev community. This is an 
idea proposed by David for GSoC2021 has already explained why the community 
would benefit from this feature.

To you and all the potential GSoC students in the community - the GSoC student 
application deadline is tomorrow, so please submit your final application 
before the deadline. Best of luck!


Regards.


From: David Jumani 
Sent: Monday, April 12, 2021 10:31
To: dev@cloudstack.apache.org 
Subject: Re: multiple SSH keys. Question to the dev community members

Hi Bikram,

That's a good idea.
I think it would benefit the users by allowing them to add their own personal 
SSH key to a VM and avoid the hassle of managing multiple shared keys for 
different VMs (across projects / domains). It also solves the problem when a 
user is removed as their key can be removed from the list, revoking their 
access without the need for a new key to be regenerated and shared. It could 
also simplify monitoring as well as automation from a central server to the VMs 
in the infrastructure without additional steps of using a specific key per VM 
or group of VMs

From: Bikram Biswas 
Sent: Saturday, April 10, 2021 7:28 PM
To: dev@cloudstack.apache.org 
Subject: multiple SSH keys. Question to the dev community members

Hi Dev community.
I want to start a discussion thread about multiple-SSH key support.
Currently, ACS supports only a single ssh key. What do you think about the 
benefits of holding multiple ssh keys. How can it help the community and the 
users, if the support for multiple ssh keys is provided?

david.jum...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #16: [DISCUSS] Work on next release

[GitBox]

onitake commented on issue #16:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-817821132


   Sorry @rhtyd I haven't had much time to look at the the k8s provider lately.
   Could you coordinate with @joschi36 instead?
   
   I'll gladly contribute code when needed, though.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] joschi36 commented on issue #16: [DISCUSS] Work on next release

[GitBox]

joschi36 commented on issue #16:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-817843326


   Hi @rafaelweingartner 
   
   For myself I would like to merge #25 to the release.
   
   Maybe @davidjumani has interest in adding #24 and #22 to the release as well?
   
   Also, I thought we don't have access to docker hub right now. 
https://github.com/apache/cloudstack-kubernetes-provider/issues/7
   And there is also no CI in place for creating docker images.
   
   I would love to take release management into my hands. However, it's hard to 
coordinate without the rights and missing pieces.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] joschi36 edited a comment on issue #16: [DISCUSS] Work on next release

[GitBox]

joschi36 edited a comment on issue #16:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/16#issuecomment-817843326


   Hi @rhtyd 
   For myself I would like to merge #25 to the release.
   
   Maybe @davidjumani has interest in adding #24 and #22 to the release as well?
   
   Also, I thought we don't have access to docker hub right now. 
https://github.com/apache/cloudstack-kubernetes-provider/issues/7
   And there is also no CI in place for creating docker images.
   
   I would love to take release management into my hands. However, it's hard to 
coordinate without the rights and missing pieces.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: ACS agent not start from ubuntu 18.04

[Rohit Yadav]

Hi,

Have you tried registering some other ISO? From the logs looks like the 
template file type is invalid. Also, check and ensure that you're able to 
read/download the iso from the webserver.

You can check the type of the file/iso that failed to be registered using "file 
http://dl.openvm.eu/cloudstack/iso/


Regards.


From: Technologyrss Mail 
Sent: Sunday, April 11, 2021 18:05
To: Rohit Yadav ; dev@cloudstack.apache.org 

Subject: Re: ACS agent not start from ubuntu 18.04


Hi,


Successfully done ACS agent running and create basic zone is ok. Now I see 
different error when I try to add iso from local web server. But when I add any 
template it is ok.


[cid:part1.8A94807A.B2D241E5@gmail.com]


[cid:part2.9DD749C4.C47097CF@gmail.com]


What can I do now? give me any idea please.


---Alamin


On 4/8/2021 1:58 PM, Rohit Yadav wrote:
Hi,

You don't have cloudbr1 bridge configured on your host. You may want to read 
through:
http://docs.cloudstack.apache.org/en/latest/conceptsandterminology/index.html#concepts-and-terminolgy
https://www.shapeblue.com/a-beginners-guide-to-cloudstack-networking/

As I've previously suggested, please check if you've or need two physical nics 
on the host. Otherwise, go to Zone -> physical network and then delete the 
additional physical network and ensure the one physical network carries all 
types of traffic (add traffic type to the physical network) and change the 
traffic label if necessary. You may read more on physical network with advanced 
zone here: 
http://docs.cloudstack.apache.org/en/latest/adminguide/networking_and_traffic.html#advanced-zone-physical-network-configuration
 If this is your test setup and you're unable to address the physical network 
changes, you may want to re-do the zone deployment from scratch again.

A shorter hack to just make it work would be to set the 
private.network.device=cloudbr0 in the agent.properties and restart the 
cloudstack-agent service, and ensure that you've only one physical network in 
the zone where the traffic label is set to cloudbr0.


Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue





From: Technologyrss Mail 

Sent: Wednesday, April 7, 2021 11:52
To: dev@cloudstack.apache.org 
; Rohit Yadav 

Subject: Re: ACS agent not start from ubuntu 18.04


Thanks.

I see /etc/cloudstack/agent/agent.properties this file default is

private.network.device' and 'public.network.device is comment.

So now I remove comment and save then start ACS agent but same error not start 
ACS agent.

[cid:part6.494B122E.77C52DCB@gmail.com]

My interface config like below.

[cid:part7.3880FB8B.10ED2C41@gmail.com]

agent log error like below.

[cid:part8.AA569330.A6EF30DB@gmail.com]

Please help me what is exact netplan config needed. ACS kvm basic network 
config official guide are not for Ubuntu 18.04 or 20.04.

---Alamin

On 4/7/2021 11:51 AM, Rohit Yadav wrote:

Hi,

Based on your screenshot of netplan config, looks like you want to use a single 
bridge with a single physical nic on KVM host. While deploying the zone did you 
configure two nics to carry guest/management/public/storage traffic? This may 
have caused CloudStack to configure cloudbr1 in 
/etc/cloudstack/agent/agent.properties on the KVM host which the 
cloudstack-agent is unable to find/use. As others have advised you can either 
fix it in the zone's physical network, and remove + re-add the host; or, if 
it's a test setup you may start from scratch again (stop management server, 
re-deploy management server DB, start management server again) and don't 
configure additional physical networks (i.e. have a single physical network or 
nic on host to carry all kinds of traffic types) while deploying the zone.


Regards.


From: Pearl d'Silva 

Sent: Wednesday, April 7, 2021 10:20
To: dev@cloudstack.apache.org 

Subject: Re: ACS agent not start from ubuntu 18.04

Hi,

To configure cloudbr1 you may use this as reference : 
http://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#configure-ubuntu-for-basic-networks(However,
 use netplan to configure it). Can you also check the agent.properties file on 
your host if 'private.network.device' and 'public.network.device' are properly 
configured. And then restart the cloudstack-agent service on the respective 
hosts.

Regards,
Pearl


From: Wei ZHOU 
Sent: Wednesday, April 7, 2021 1:03 AM
To: dev@cloudstack.apache.org 

Subject: Re: ACS agent not start from ubuntu 18.04

you need t

Re: [DISCUSS] Using qemu-kvm vs qemu-kvm-ev with CloudStack

[Andrija Panic]

qemu-kvm-ev from regular CentOS SIG repo will NOT support
live-storage-migration.

Only the equivalent qemu-kvm-ev from the oVirt repo will support this.

This drifts far away from the stock CentOS 7 that most people are using, or
are using by default.
I would leave up to the user to upgrade their infra based on their testing
of these external qemu version (that obviously works fine for various users
across various companies using CentOS 7).

But I would still continue to "disable' the tests in the Marvin suite, like
they were disabled so far.

Again, please note only the oVirt version of qemu-kvm-ev is the good one,
the "regular one" from the the CentOS SIG repo us useless in sense of
live-storage migration (unless something has changed last 3 months that I'm
not aware of)

+1 for Doc update to use oVirt qemu-kmv-ev in production (and test it...)

On Sun, 11 Apr 2021 at 04:47, Marcus  wrote:

> Yes, +1 on EV. It is more current, better maintained and I think it is
> generally considered the go-to for EL based hypervisors (largely due to the
> oVirt use).
>
>
> On Saturday, April 10, 2021, Rohit Yadav 
> wrote:
>
> > Great, thanks for sharing Simon. If we've consensus and there are no
> > objections I would propose we update the docs around CentOS/KVM to use
> the
> > -ev packages.
> >
> > Let's hear from others.
> >
> >
> > Thanks and regards.
> >
> > 
> > From: Simon Weller 
> > Sent: Friday, April 9, 2021 19:09
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org 
> > Subject: Re: [DISCUSS] Using qemu-kvm vs qemu-kvm-ev with CloudStack
> >
> > Hi Rohit,
> >
> > We've been using ev exclusively for a few years now. Our main reason was
> > in order to support features we upstreamed around KVM iop limits a couple
> > of years back.
> > Short of one challenge that was addressed on the ACS side a while ago
> > related to the patchviasocket integration, it has worked very well and
> has
> > been very stable.
> >
> > -Si
> >
> > 
> > From: Rohit Yadav 
> > Sent: Friday, April 9, 2021 2:26 AM
> > To: dev@cloudstack.apache.org ;
> > us...@cloudstack.apache.org 
> > Subject: [DISCUSS] Using qemu-kvm vs qemu-kvm-ev with CloudStack
> >
> > All,
> >
> > We've recently seen some tests around live VM with storage failing on
> > CentOS7 which is addressed in this PR:
> > https://github.com/apache/cloudstack/pull/4801
> >
> > Some users have added on the original issue ticket that it works with
> > qemu-kvm-ev on CentOS:
> > https://github.com/apache/cloudstack/issues/4757#issuecomment-812595973
> >
> > I also see many other IaaS platforms notably oVirt using qemu-kvm-ev, is
> > there any interest and argument in saying we test and update our docs to
> > advise users to use qemu-kvm-ev on CentOS? Are there any CloudStack users
> > who want to share their experience with it who may be using it already?
> >
> > The installation steps don't require configuring any 3rd party repository
> > manually and usually done with:
> >
> > yum install centos-release-qemu-ev
> > yum install qemu-kvm-ev
> >
> > Additional references:
> > https://lists.centos.org/pipermail/centos-virt/2015-October/004717.html
> > (what is qemu-kvm vs qemu-kvm-ev)
> > https://wiki.centos.org/SpecialInterestGroup/Virtualization (the SIG
> that
> > is behind the qemu-kvm-ev repository)
> >
> > Thanks and regards.
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >
>


-- 

Andrija Panić