Hi,
There is no IP address in this path. However, I have added several IP
ranges in Infrastructure -> Zones -> Zone1 -> Physical Networks -> Physical
Network 1 -> Guest -> GuestNetwork1 -> View IP Ranges
Thanks
On Sun, Sep 8, 2019 at 11:08 AM Nii Apleh Lartey wrote:
> Hello,
>
> If it is for p
Internal LB, is as good as non-existent - just being honest... Again, it's
used in VPC. Effectively a new mini VM with haproxy is created, but last
time I checked, had no health checks at all etc
On Sun, Sep 8, 2019, 03:29 Fariborz Navidan wrote:
> Hi,
>
> There is no IP address in this path. Ho
On 9/8/19 5:26 AM, Andrija Panic wrote:
> Maaany release ago, deleting Ceph volume snap, was also only deleting it in
> DB, so the RBD performance become terrible with many tens of (i. e. Hourly)
> snapshots. I'll try to verify this on 4.13 myself, but Wido and the guys
> will know better...
I
Hello,
I have removed VR and restarted network. VR is keeping held in Starting
state and following entries are continuously being logged into
management-server.log. It is filling Gigabytes of disk!!
2019-09-08 18:07:49,654 DEBUG [c.c.a.m.ClusteredAgentAttache]
(AgentManager-Handler-6:null) (logid
And these exceptions are logged in agent log:
2019-09-08 17:42:55,005 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
(logid:) Connected to the host: 51.91.247.86
2019-09-08 17:54:24,154 INFO [cloud.agent.Agent]
(AgentShutdownThread:null) (logid:) Stopping the agent: Reason = sig.kill
2019-09-08
Thanks for the feedback, Andrija. It looks like delete was not totally
supported then (am I missing something?). I will take a look into this and
open a PR adding propper support for rbd snapshot deletion if necessary.
Regarding the rollback, I have tested it several times and it worked;
however,
Thx Gabriel for extensive feedback.
Actually my ex company added the code to really delete a RBD snap back in
2016 or so, was part of 4.9 if not mistaken. So I expect the code is there,
but probably some exception is happening or regression...
Cheers
On Sun, Sep 8, 2019, 09:31 Gabriel Beims Bräsc
"(Agent-Handler-1:null) (logid:) Connection with libvirtd is broken:
invalid"
Perhaps try to restart your libvird or check its logs - your setup might be
in smoke...
Sun, Sep 8, 2019, 09:24 Fariborz Navidan wrote:
> And these exceptions are logged in agent log:
>
> 2019-09-08 17:42:55,005 INFO
agent is now seem to work. It reports CPU/Memory utilization right. However
VM is still in Starting state and the r-167-VM is still not showing with
virsh list --all.
On Sun, Sep 8, 2019 at 10:52 PM Andrija Panic
wrote:
> "(Agent-Handler-1:null) (logid:) Connection with libvirtd is broken:
> inv
All,
I am here in Las Vegas and plan to video all of the CCC talks. I’ll then be
posting those on the ASF YouTube channel.
As I have the equipment here, I would also like to try and film some
footage and interviews that I can use to create some Cloudstack marketing
videos - that we could use on t
That is interesting, but you need to watch out for image consents when
recording people. I do not know how this is being handled in the event
(ApacheCon) and sub-events (e.g. CCC).
On Sun, Sep 8, 2019 at 6:05 PM Andrija Panic
wrote:
> All,
>
> I am here in Las Vegas and plan to video all of the
11 matches
Mail list logo
