ts.openstack.org/pipermail/openstack-dev/2017-April/115292.html
--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
__
OpenStack Development Mailing List (not for usage questions)
will help with this question.
Thank you!
On 6/23/18 8:41 PM, Jay Bryant wrote:
On Sat, Jun 23, 2018, 9:39 AM Volodymyr Litovka <mailto:doka...@gmx.com>> wrote:
Dear friends,
I did some tests with making volume available without stopping VM.
I'm
using CEPH and th
with minimized downtime
(it's just reboot, not manual stop/update/start).
Thank you.
--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
__
OpenStack Development Mailing List (not for usage
;subnet-1" goes over "subnet-2" (through NAT) and, thus, VM in Subnet-1
can't access VR - it "pings" local address (25.0.0.1) while replies
return from another (NAT) address.
Whether this behaviour can be safely changed by using "ip route add
[...] metric " ins
another set of resources. If Heat
will provide basic set of functions within basic LBaaS framework and,
sometimes, richer set within "NG LBaaS" framework - the only I can say:
it will be great.
Thanks.
https://bugs.launchpad.net/heat/+bug/1737567
--
Volodymyr Litovka
"
em).
Seems I'm missing something.
And two related questions:
* which method to provide API is more preferable - WSGI or standalone
octavia-api process?
* how to be sure that Octavia code matches Pike version? I'm using
"pip install octavia" and it's v1.0.1 at
stener: { get_resource: listener }
pm1:
type: OS::Neutron::LBaaS::PoolMember
properties:
address: { get_attr: [ n1, first_address ]}
pool: { get_resource: pool }
protocol_port: { get_param: pool_port }
subnet: { get_resource: lan-subnet }
pm2:
type: OS::N
thmonitor
show 71cc7956-7c54-448a-96a7-709905c2bf4f
Unable to locate 71cc7956-7c54-448a-96a7-709905c2bf4f in healthmonitors
Be informed and can this impact something else?
Thank you.
--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
__
Hi colleagues,
found the solution, it need to be done manually. No corresponding
Octavia configuration responsible for this.
Everything works, thank you :-)
On 11/27/17 11:30 AM, Volodymyr Litovka wrote:
Hello colleagues,
I think I'm missing something architectural in LBaaS / Octavia
n closed
(project's) networks with Internet using Octavia / LBaaS?
Thank you!
--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
__
OpenStack Development Mailing List (not for usage qu
Please, disregard this message - I've found that part of networking
resides in namespace.
On 11/7/17 5:54 PM, Volodymyr Litovka wrote:
Dear colleagues,
while trying to setup Octavia, I faced the problem of connecting
amphora agent to VIP network.
*Environment:
*Octavia 1.0.1 (installed
': u'network-v
if-plugged', u'server_uuid': u'98ae591b-0270-4625-95eb-a557c1452eef',
u'code': 200}
*Octavia-worker.log* is available at the following link:
https://pastebin.com/44rwshKZ
*Q**uestion**s are* - any ideas on what is happening and which
12 matches
Mail list logo