Hi Cinder team,
Since the 80 port or our log server have some issue to be accessed from the
public, we have changed the port from 80 to 8088.
* So if you opened a link like
http://182.138.104.27/huawei-18000-iscsi-dsvm-tempest-full/70, please change
the access port to 8088,
* l
Yes! There is a block at 80 port, and if you change it to 8088, for example
:
Change http://182.138.104.27/huawei-18000-iscsi-dsvm-tempest-full/70
to http://182.138.104.27:8088/huawei-18000-iscsi-dsvm-tempest-full/70
then it works!
And I have updated my apache configuration to ajust this.
Li
On 04/05/2015 09:17 PM, Jay Pipes wrote:
On 03/30/2015 03:16 AM, Balázs Gibizer wrote:
Hi,
I have the following scenario. I have an application consisting of
multiple VMs on different compute hosts. The admin puts one of the
hosts into maintenance mode (nova-manage service disable ...) because
On 18:20 Mon 23 Mar , Diem Tran wrote:
> Hello Cinder team,
>
> Oracle ZFSSA CI has been reporting since March 20th. Below is a link
> to the list of results the CI already posted:
>
> https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z
>
> Our CI system will be running and r
Just trying this out for fun (Mike's reply made me curious)
A lot of the link on the initial note weren't working for me, but this one
did: https://review.openstack.org/#/c/169781/
and it's CI reports seem to work as well. They route me to:
http://182.138.104.29:8088/huawei-18000-fc-dsvm-tempest
On 12:47 Sat 04 Apr , liuxinguo wrote:
> Hello Cinder team,
>
> · Huawei Volume CI has posted to about forty cinder reviews from
> April 1 to now and will keep reporting stably.
> ·
> · It now runs 304 tests, passed 293 and skipped 11.
>
> The following are links to the cinde
+1 from me. Since we don't have ENROLL state as per the state machine, I
think it should be MANAGEABLE when we enroll a node. At least, it can also
prevent nodes getting into a ready state even before an operator getting
hands on it.
One comment on #2. Before we make a new client release with v
On 03/30/2015 03:16 AM, Balázs Gibizer wrote:
Hi,
I have the following scenario. I have an application consisting of
multiple VMs on different compute hosts. The admin puts one of the
hosts into maintenance mode (nova-manage service disable ...) because
there will be some maintenance activity o
It heavily depends on your swift and network setup. We see better
throughout without compression, by about 20% if I remember correctly.
On 6 Apr 2015 04:17, "Jae Sang Lee" wrote:
> Send without compression is more slower because it send a large data.
> In my environment, send 10GB disk to swift e
Send without compression is more slower because it send a large data.
In my environment, send 10GB disk to swift except compression spent 6min
40sec but with compression 4min 13sec.
2015-04-02 23:16 GMT+09:00 Murali Balcha :
> Just curious. What is the overhead of compression and other backup
>
Hi Everyone,
After shadowing Doug for a while, It's going to be a really hard job
filling Doug's shoes. I am very thankful and very glad we had him so
long to guide us. I'd like to continue his good work going forward.
We've achieved a lot last couple of cycles, and the proof is the
almost empty
Brant,
I run profimp with and without patch
https://review.openstack.org/#/c/164066/:
And it really works well:
before 170ms:
http://boris-42.github.io/keystone/before.html
after 76ms:
http://boris-42.github.io/keystone/after.html
Best regards,
Boris Pavlovic
On Fri, Apr 3, 2015 at 2:44 AM,
Hi everyone,
I am announcing my candidacy for Documentation PTL.
I have been contributing to the OpenStack documentation project since 2013, and
have been a core contributor since early 2014. During that time I have been
supporting and promoting the OpenStack documentation community in the sout
Hi folks,
I'd like to announce my candidacy as PTL for Murano [1].
I was handling PTL responsibilities in this release cycle so far,
after Ruslan Kamaldinov (who was handling them in Juno cycle) hand
over them to me on OpenStack Summit in Paris. I am working on Murano
since it's kick-off two year
Hi,
After talking to several customers, we noticed that there is a solid
requirement that choosing a compute node would take into account other
attributes as NIC's attributes and capabilities ( speed, RDAM enable,
supported link modes and etc... ).
I was searching around old BP, and was thinki
I am using latest git version (after
https://review.openstack.org/#/c/165716/ merge):
There are 18 tests failing( (logging noop driver) with latest changes
Attaching tempest log files.
Thanks
Santosh
stack@devstack:~/neutron-lbaas$ tox -e tempest
tempest develop-inst-nodeps: /opt/stack/neutron
16 matches
Mail list logo
