I test the freezer backup with lvm snapshot. The command hava no error. but It
doesn't seem to work
Do Freezer support backup with lvm snapshot at present?
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : o
when I test the 'MongoDB Backup With LVM Snapshot'
from
https://docs.openstack.org/freezer/queens/user/freezer-agent.html#mongodb-backup-with-lvm-snapshot
i got the error "CRITICAL freezer.main [-] Critical Error: 'me'"
log detail:
2018-03-19 14:50:05.597 1085 INFO freezer.mode.mongo [-] MongoD
I want to create a container use Zun, like the docker command
docker run -p ip:hostPort:containerPort OPTIONS
so i can access the container_port via hostip:hostport ，but i can't find some
similar commands in Zun Command Line
usage: zun run [-n ] [--cpu ] [-m ] [-e ]
[--workdi
e
over a block device from another server. So, if you unmount on your first
server, you can mount
on the second and you will see your file.
Arne
On 06 Mar 2018, at 09:53, 谭 明宵
mailto:tanmingx...@outlook.com>> wrote:
I installed the openstack queens use devstack. I want to test the &q
I installed the openstack queens use devstack. I want to test the "Cinder
Multi-Attach" function
1. create a multiattach volume
```
# cinder type-create multiattach
# cinder type-key multiattach set multiattach=" True"
# cinder create 10 --name multiattach-volume --volume-type
```
2. attache
View all services:
sudo systemctl status "devstack@*"
Track the log of a given service：
journalctl -f --unit devstack@n-cpu.service
Track logs of a group of services：
journalctl -f --unit devstack@n-*
Trace the associated service log：
journalctl -f --unit devstack@n-cpu.service --unit devstack
ion failed for
token
the keystone conf problem?
在2017年9月21日 18:21，Jens Harbott<mailto:j.harb...@x-ion.de>
写道：
2017-09-21 11:32 GMT+02:00 谭 明宵 :
>
> I had HA setup for placement api to work on high availability enviornment by
> using HAproxy on three controller nodes
>
> v
I had HA setup for placement api to work on high availability enviornment by
using HAproxy on three controller nodes
vim /etc/haproxy/haproxy.cfg
listen nova_placement_cluster
bind 0.0.0.0:8778
http-request del-header X-Forwarded-Proto
server controller01 192.168.105.10:
