Hi Nixon,
In an isolated guest network you could create a guest instance and use it as a
NAS?
In a shared network you will have more flexibility in using existing NAS in the
cloudstack provisioned guest instances.
-Jithin
From: Nixon Varghese K S
Date: Saturday, 27 April 2024 at 7:04 AM
To:
For the SSVM issue this article might help you, specifically check for the
management server IP connectivity on port 8250.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting
Regarding the login issue you mentioned I am not sure about
When using advanced networking, I believe there's an option to create site
to site tunnel.
Maybe you can establish a tunnel between the isolated network via the VR and
onsite DC firewall/router.
But of course, it's going through public/Internet which might hinder the
network performance
I'm currently learning CS and setting up a POC environment.
Two system VMs is running on the same KVM host in my 3 KVM host cluster.
However, the secondary storage VM Agent state is shown as Connecting.
I've SSH into the secondary storage VM and can assure that it can reach the
Internet and
Hi Fernando,
It’s a wildcard that is being replaced by a wildcard :) But the sslcerts table
is empty in the database so something went wrong.
In the meantime I found my issue, the strange part is that the webgui does not
check on if the certificate is correct, as I was missing the:
-END
Jummy,
I understand.
Many times when you change the certificate you start using a Domain
Validation certificate (DV SSL) instead of a Wilcard certificate. If the
global URL configuration is set to dynamic, the certificate does not work
and the console service does not work either.
---
Fernando.
Hi,
It’s an existing deployment, I just tried renewing the certificate, before I
started with the renewal it worked fine, so I think I borked something but what
it is, I don’t know, I just followed the document I made before for myself.
--
Jimmy
From: Fernando Alvarez
Date: Monday, 29 April
Hi Jimmy,
Check these values in the global setting:
consoleproxy.url.domain domain used for CPVM
consoleproxy.sslEnabled Switches SSL configuration of the CPVMon / off
And check if the URL configuration is set to Static or Dynamic. If it is
Dynamic remember that you need a Wildcard SSL
Hi Ruben,
That made me being able to login :)
I seem to be getting this:
Apr 29 12:25:49 v-144-VM systemd[1]: cloud.service: Main process exited,
code=exited, status=1/FAILURE
Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,272 INFO Agent:314 -
Stopping the agent: Reason = sig.kill
Apr 29
Thanks for the reply Ivan. We would like to develop this feature for our
business and sponsor to the ACS community so that others can also be
benefited. Any developer help in the community to add this feature (we will
pay for it) would be greatly appreciated.
Regards
Loges
On Tue, Apr 23, 2024
Jimmy, you can run "cloudstack-ssh 169.x.x.x" or "ssh -i
/root/.ssh/id_rsa.cloud -p 3922 root@169.x.x.x" from the hypervisor running
the system VM to SSH into the system VM.
On Mon, Apr 29, 2024 at 2:09 PM Jimmy Huybrechts
wrote:
> Hi,
>
> So I replaced the SSL certficate today since it uses
Hi,
So I replaced the SSL certficate today since it uses lets encrypt.
My secondary storage worked fine after recreation, but it seems my consoleproxy
doesn’t as it shows agent state disconnected, connecting, disconnected.
Now obviously I don’t have any console now so I can’t see what is wrong
Hi Vivek,
I think you can tune the following global settings to regenerate CloudStack's
root-ca certificates with chosen cipher/algorithm and key size: (depending on
the ACS version if it has CA framework)
ca.framework.cert.signature.algorithm
ca.framework.cert.keysize
(for an already
Hello Folks,
Our security team has highlighted that services running on port 8250 supports
the use of SSL ciphers that offer medium strength encryption. Nessus regards
medium strength as any encryption that uses key lengths at least 64 bits and
less than 112 bits,
It is considerably easier
GitHub user dR3b edited a comment on the discussion: Same network for VMs as
KVM hosts?
@weizhouapache Thanks! This works, but deletes all the IPtable rules on the
host. I have not created any rules myself. These rules must be from Cloudstack
or UFW.
GitHub link:
GitHub user dR3b added a comment to the discussion: Same network for VMs as KVM
hosts?
@weizhouapache Thanks! This works, but deletes all Iptables rules on the host.
I have not created any rules myself. These rules must be from Cloudstack or UFW.
GitHub link:
GitHub user weizhouapache added a comment to the discussion: Same network for
VMs as KVM hosts?
@dR3b
a user has replied to to this thread in the users mailing list, no idea why it
is not present here
GitHub user dR3b edited a comment on the discussion: Same network for VMs as
KVM hosts?
@weizhouapache Yes!
```
root@nuc1:/# cat /proc/sys/net/ipv4/ip_forward
1
```
GitHub link:
https://github.com/apache/cloudstack/discussions/8998#discussioncomment-9258076
This is an automatically
Yes, in theory it sounds good, but the IPv6 overlap check seems to block
everything. I think our best way forward is to move the network to ROOT and
ensure all free IPs are allocated in the db so that other users cannot use
the network.
Thanks for thinking along Wei, Daan and Pearl!
On Fri, Apr
i noticed similar issue on 4.19 ... iptables -F on the host resolved it...
seems somthing wasnt being setup right with rules
On Monday 29 April 2024 02:18:03 AM (-04:00), dR3b (via GitHub) wrote:
>
> GitHub user dR3b edited a comment on the discussion: Same network for VMs as
> KVM hosts?
>
GitHub user bkrajendra edited a comment on the discussion: Host-HA vs VM-HA
(was: KVMHAMonitor getting initialized without host ha enabled)
CloudStack 4.17.0.1
Recently I also started getting this issue:
```
Apr 27 07:50:33 host java: WARN [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:)
GitHub user bkrajendra edited a comment on the discussion: Host-HA vs VM-HA
(was: KVMHAMonitor getting initialized without host ha enabled)
CloudStack 4.17.0.1
Recently I also started getting this issue:
```
Apr 27 07:50:33 pnqsun java: WARN [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:)
GitHub user dR3b edited a comment on the discussion: Same network for VMs as
KVM hosts?
@weizhouapache
Thanks! After several pages in the documentation[1], I was able to complete the
installation.
- [x] System-VM consoleproxy, Up and running
- [x] System-VM secondarystoragevm, Up and
GitHub user bkrajendra added a comment to the discussion: Host-HA vs VM-HA
(was: KVMHAMonitor getting initialized without host ha enabled)
Recently I also started getting this issue:
```
Apr 27 07:50:33 pnqsun java: WARN [kvm.resource.KVMHAMonitor] (Thread-1:)
(logid:) Write heartbeat for
GitHub user dR3b added a comment to the discussion: Same network for VMs as KVM
hosts?
Yes!
```
root@nuc1:/# cat /proc/sys/net/ipv4/ip_forward
1
```
GitHub link:
https://github.com/apache/cloudstack/discussions/8998#discussioncomment-9258076
This is an automatically sent email for
25 matches
Mail list logo
