New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix general typos #668

Merged
merged 1 commit into from Oct 19, 2017
Jump to file or symbol
Failed to load files and symbols.
+17 −17
Diff settings

Always

Just for now

@@ -5,7 +5,7 @@ High Availability storage (HA storage) is a storage system that is continuously
OpenEBS Jiva Volume is a controller with one or more replicas. The controller is an iSCSI target whereas the replica plays the role of disk. The controller exposes the iSCSI target while the actual data is written. The controller and each individual replica run inside a dedicated container.
OpenEBS Jiva Volume controller exists as a single instance but there can be multiple instances of OpenEBS Jiva volume replicas. Peristent data is synchronized between replicas.
OpenEBS Jiva Volume controller exists as a single instance but there can be multiple instances of OpenEBS Jiva volume replicas. Persistent data is synchronized between replicas.
OpenEBS Jiva Volume HA is based on various scenarios as explained in the following sections.
@@ -109,7 +109,7 @@ Apply the percona pod yaml using the following commands.
cd demo/percona
kubectl apply -f demo-percona-mysql-pvc.yaml
Verify that the OpenEBS storage pods, that is, the jiva controller and jiva replicas are created and the percona pod is running succesfully using the following commands.
Verify that the OpenEBS storage pods, that is, the jiva controller and jiva replicas are created and the percona pod is running successfully using the following commands.
::
@@ -245,7 +245,7 @@ The above command creates the following, which can be verified using the corresp
- Creates an OpenEBS Volume and mounts to the Jupyter Server Pod (/mnt/data) (kubectl get pvc) (kubectl get pv) (kubectl get pods)
- Exposes the Jupyter Server to external world via the http://<NodeIP>:32424 (NodeIP is any of the nodes external IP) (kubectl get pods)
Verify that the OpenEBS storage pods, that is, the jiva controller and jiva replicas are created and the jupyter pod is running succesfully using the following commands.
Verify that the OpenEBS storage pods, that is, the jiva controller and jiva replicas are created and the jupyter pod is running successfully using the following commands.
::
@@ -24,15 +24,15 @@ New v0.4.0 Features
* OpenEBS Volume - Dynamic Provisioner is merged into kubernetes-incubator/external-storage project
* OpenEBS Maya API Server uses the Kubernetes scheduler logic to place OpenEBS Volume Replicas on different nodes
* OpenEBS Maya API Server can be customized by providing ENV options through K8s YAML file for default replica count and jiva image to be used
* OpenEBS user documentation is avilable at http://openebs.readthedocs.io/en/latest/
* OpenEBS user documentation is available at http://openebs.readthedocs.io/en/latest/
* OpenEBS now supports deployment on AWS, along with previously supported Google Cloud and On-premise setups
* OpenEBS Vagrant boxes are upgraded to support Kubernetes version 1.7.5
* OpenEBS can now be deployed within a minikube setup
Issues Fixed in v0.4.0
==============================
* #166 (https://github.com/edorid): openebs-k8s-provisioner goes into crashloopbackoff, during the first volume creation
* #176 (https://github.com/maikotz): OpenEBS PV is unreachable after one of the replica becames unreachable.
* #176 (https://github.com/maikotz): OpenEBS PV is unreachable after one of the replica becomes unreachable.
Known Issues in v0.4.0
==============================
@@ -76,4 +76,4 @@ Notes for Contributors
* The deployment and e2e functionality will continue to be located in *openebs/k8s* and *openebs/e2e* respectively.
* openebs/maya will act as a single repository for hosting different OpenEBS Storage Control plane (orchestration) components.
* New /metrics handlers are being added to OpenEBS components to allow integration into tools like Prometheus.
* *openebs/maya/cmd/maya-agent* which will be deployed as a deamon-set running along-side kubelet is being developed. maya-agent will augument the kubelet with storage management functionality.
* *openebs/maya/cmd/maya-agent* which will be deployed as a deamon-set running along-side kubelet is being developed. maya-agent will augument the kubelet with storage management functionality.
Copy path View file
@@ -312,7 +312,7 @@ retry_files_enabled = False
#
#pipelining = False
# Control the mechanism for transfering files
# Control the mechanism for transferring files
# * smart = try sftp and then try scp [default]
# * True = use scp only
# * False = use sftp only
Copy path View file
@@ -71,7 +71,7 @@ Jenkins application for Slack must be installed and configured.
- Enter the token provided in the Jenkins application for Slack in _Integration Token_ field.
- Enter the slack channel details in _Channel_ field.
- Click _Test Connection_. The slack channel should be getting a notification from Jenkins.
- If a notification is recieved then click _Apply_ and _Save_.
- If a notification is received then click _Apply_ and _Save_.
- The configuration for the Slack Plugin is complete.
## Continuous Integration - Step 4: Creating The Jobs
Copy path View file
@@ -41,7 +41,7 @@ node.startup = manual
# For "automatic" startup nodes, setting this to "Yes" will try logins on each
# available iface until one succeeds, and then stop. The default "No" will try
# logins on all availble ifaces simultaneously.
# logins on all available ifaces simultaneously.
node.leading_login = No
# *************
@@ -14,7 +14,7 @@ In this guide, we will walk you through the following:
## Prerequisites
Identify 3 Ubuntu 16.04 machines (either Virtual Machines or Physcial Machines) which will be used for OpenEBS Cluster. In the examples below, we will assume the following hostnames and IP address. Please replace this with your machine details.
Identify 3 Ubuntu 16.04 machines (either Virtual Machines or Physical Machines) which will be used for OpenEBS Cluster. In the examples below, we will assume the following hostnames and IP address. Please replace this with your machine details.
```
master-01 ( 172.28.128.4)
@@ -88,7 +88,7 @@ data:
############################# Log Basics #############################
# A comma seperated list of directories under which to store log files
# A comma separated list of directories under which to store log files
log.dirs=/tmp/kafka-logs
# The default number of log partitions per topic. More partitions allow greater
Copy path View file
@@ -122,7 +122,7 @@ kubectl apply -f demo-percona-mysql-pvc.yaml
```
Verify that the openebs storage pods, i.e., the jiva controller and jiva replicas
are created and the percona pod is running succesfully
are created and the percona pod is running successfully
```
karthik@MayaMaster:~$ kubectl get pods
@@ -70,7 +70,7 @@ EOF
}
# Code:
# Check whether we recieved the User and Master hostnames else Show usage
# Check whether we received the User and Master hostnames else Show usage
# Uses the long form of arguments now
if (($# == 0)); then
@@ -51,7 +51,7 @@ log() {
echo -ne $* >&1
}
#Dump the debug information into a seperate logger
#Dump the debug information into a separate logger
#TBD : Check how to push this information into K8s loggers
debug() {
if [ ${OEBSDEBUG} ]; then echo -e $* >> ${OLOGS_DIR}/openebs-iscsi.log; fi
@@ -40,7 +40,7 @@ EOF
}
# Code:
# Check whether we recieved the User and Master hostnames else Show usage
# Check whether we received the User and Master hostnames else Show usage
# Uses the long form of arguments now
if (($# == 0)); then
@@ -57,7 +57,7 @@ rules:
verbs: ["get", "list", "watch"]
# nonResourceURLs are endpoints that don’t map to a traditional resource.
# Things like /ui/ or /apis or /swagger.json that are used for redirects
# Prometheus by default look for /metrics endpoint for the differnet IP's.
# Prometheus by default look for /metrics endpoint for the different IP's.
- nonResourceURLs: ["/metrics"]
verbs: ["get"]
---
Copy path View file
@@ -102,7 +102,7 @@ The connection error is expected. The next step will configure the kubectl to co
vagrant ssh kubemaster-01 -c "cat ~/.kube/config" > demo-kube-config
```
*Note: If you have a single Kubernetes cluster on your host, you could copy the demo-kube-config to ~/.kube/config, and avoid specifiying the parameter --kubeconfig in the kubectl commands*
*Note: If you have a single Kubernetes cluster on your host, you could copy the demo-kube-config to ~/.kube/config, and avoid specifying the parameter --kubeconfig in the kubectl commands*
### Verify
ProTip! Use n and p to navigate between commits in a pull request.