You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This reverts commit 5a5cbf7.
This breaks on a default openstack install on Ubuntu 12.10,
revert for now until this can be cleaned up to work out of the
box.
Change-Id: I185509cc30bd28e920cdab60fc92129949bd6b0d
Copy file name to clipboardExpand all lines: README.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,21 +85,19 @@ Example (Qpid):
85
85
86
86
# Swift
87
87
88
-
Swift is enabled by default configured with only one replica to avoid being IO/memory intensive on a small vm. When running with only one replica the account, container and object services will run directly in screen. The others services like replicator, updaters or auditor runs in background.
88
+
Swift is not installed by default, you can enable easily by adding this to your `localrc`:
89
89
90
-
If you would like to disable Swift you can add this to your `localrc` :
If you want a minimal Swift install with only Swift and Keystone you can have this instead in your `localrc`:
95
93
96
94
disable_all_services
97
-
enable_service key mysql s-proxy s-object s-container s-account
98
-
99
-
If you only want to do some testing of a real normal swift cluster with multiple replicas you can do so by customizing the variable `SWIFT_REPLICAS` in your `localrc` (usually to 3).
95
+
enable_service key mysql swift
100
96
101
-
# Swift S3
97
+
If you use Swift with Keystone, Swift will authenticate against it. You will need to make sure to use the Keystone URL to auth against.
102
98
103
99
If you are enabling `swift3` in `ENABLED_SERVICES` devstack will install the swift3 middleware emulation. Swift will be configured to act as a S3 endpoint for Keystone so effectively replacing the `nova-objectstore`.
104
100
105
101
Only Swift proxy server is launched in the screen session all other services are started in background and managed by `swift-init` tool.
102
+
103
+
By default Swift will configure 3 replicas (and one spare) which could be IO intensive on a small vm, if you only want to do some quick testing of the API you can choose to only have one replica by customizing the variable `SWIFT_REPLICAS` in your `localrc`.
0 commit comments