ProHoster > Блог > administratio > "Novi Epics". Elephantum in partibus manducamus

"Novi Epics". Elephantum in partibus manducamus

"Novi Epics". Elephantum in partibus manducamus

In hoc articulo constituam ambitum laborantem ad ludum "Epics" evolvendum, ipsumque ludum frangam in partes usui aptas in OpenFaaS. Omnes machinationes in Linux faciam, Kubernetes in minikube VirtualBox explicabo. Mihi opus machina habet 2 processus metretas et 12GB RAMI, utor SSD ut systematis orbis. Debian VIII utar ut systema principale evolutionis meae, cum emacs, sudo, git et fasciculis virtualis inauguratis, reliqua omnia ex GitHub aliisque fontibus demptione instituentur. Has applicationes in /usr/loci/bin instituemus, nisi aliud specificetur. Let's get started!

Praeparans opus environment

installing Go

Mandata ex rutrum sequimur:

$ curl -L0 https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz -o go.tar.gz
$ sudo tar -C /usr/local -xzf go.tar.gz
$ echo 'export PATH=$PATH:/usr/local/go/bin' >> ~/.profile

Reprehendo functionality:

$ mkdir -p ~/go/src/hello && cd ~/go/src/hello
$ echo 'package main

import "fmt"

func main() {
fmt.Printf("hello, worldn")
}' > hello.go
$ go build
$ ./hello
hello, world

Installing faas-cli

Mandata ex rutrum sequimur:

$ curl -sSL https://cli.openfaas.com | sudo -E sh
x86_64
Downloading package https://github.com/openfaas/faas-cli/releases/download/0.11.3/faas-cli as /tmp/faas-cli
Download complete.

Running with sufficient permissions to attempt to move faas-cli to /usr/local/bin
New version of faas-cli installed to /usr/local/bin
Creating alias 'faas' for 'faas-cli'.
  ___                   _____           ____
 / _  _ __   ___ _ __ |  ___|_ _  __ _/ ___|
| | | | '_  / _  '_ | |_ / _` |/ _` ___ 
| |_| | |_) |  __/ | | |  _| (_| | (_| |___) |
 ___/| .__/ ___|_| |_|_|  __,_|__,_|____/
      |_|

CLI:
 commit:  73004c23e5a4d3fdb7352f953247473477477a64
 version: 0.11.3

Accedit, quod effici potest ut vercundus-completio:

faas-cli completion --shell bash | sudo tee /etc/bash_completion.d/faas-cli

Installing et configurans Kubernetes

Ad progressionem, minikube satis est, sic eam institue et kubelet in /usr/locum/bin, et gubernaculum ad applicationes instituendas;

$ curl https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 -o minikube && chmod +x minikube && sudo mv minikube /usr/local/bin/
$ curl https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl -o kubectl && chmod +x kubectl && sudo mv kubectl /usr/local/bin/
$ curl https://get.helm.sh/helm-v3.0.2-linux-amd64.tar.gz | tar -xzvf - linux-amd64/helm --strip-components=1; sudo mv helm /usr/local/bin

Minikube launch:

$ minikube start
  minikube v1.6.2 on Debian 8.11
  Automatically selected the 'virtualbox' driver (alternates: [])
  Downloading VM boot image ...
    > minikube-v1.6.0.iso.sha256: 65 B / 65 B [--------------] 100.00% ? p/s 0s
    > minikube-v1.6.0.iso: 150.93 MiB / 150.93 MiB [-] 100.00% 5.67 MiB p/s 27s
  Creating virtualbox VM (CPUs=2, Memory=8192MB, Disk=20000MB) ...
  Preparing Kubernetes v1.17.0 on Docker '19.03.5' ...
  Downloading kubeadm v1.17.0
  Downloading kubelet v1.17.0
  Pulling images ...
  Launching Kubernetes ...  Waiting for cluster to come online ...
  Done! kubectl is now configured to use "minikube"

reprehendo:

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE
kube-system   coredns-6955765f44-knlcb           1/1     Running   0          29m
kube-system   coredns-6955765f44-t9cpn           1/1     Running   0          29m
kube-system   etcd-minikube                      1/1     Running   0          28m
kube-system   kube-addon-manager-minikube        1/1     Running   0          28m
kube-system   kube-apiserver-minikube            1/1     Running   0          28m
kube-system   kube-controller-manager-minikube   1/1     Running   0          28m
kube-system   kube-proxy-hv2wc                   1/1     Running   0          29m
kube-system   kube-scheduler-minikube            1/1     Running   0          28m
kube-system   storage-provisioner                1/1     Running   1          29m

Installing OpenFaaS

In tincidunt suadeo creandi 2 spatiis nominalibus ad operandum:

$ kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml
namespace/openfaas created
namespace/openfaas-fn created

Repositio ad galeam adde:

$ helm repo add openfaas https://openfaas.github.io/faas-netes/
"openfaas" has been added to your repositories

Charta facultatem habet tesseram ponendi ante institutionem, ea utamur et notitias accessus ut arcanum k8s servent;

$ PASSWORD=verysecurerandompasswordstring
$ kubectl -n openfaas create secret generic basic-auth --from-literal=basic-auth-user=admin --from-literal=basic-auth-password="$PASSWORD"
secret/basic-auth created

Explicemus:

$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "openfaas" chart repository
Update Complete.  Happy Helming!
$ helm upgrade openfaas --install openfaas/openfaas --namespace openfaas --set functionNamespace=openfaas-fn --set generateBasicAuth=false
Release "openfaas" does not exist. Installing it now.
NAME: openfaas
LAST DEPLOYED: Fri Dec 25 10:28:22 2019
NAMESPACE: openfaas
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
To verify that openfaas has started, run:

  kubectl -n openfaas get deployments -l "release=openfaas, app=openfaas"

Post aliquod tempus praeceptum propositum curritur;

$ kubectl -n openfaas get deployments -l "release=openfaas, app=openfaas"
NAME                READY   UP-TO-DATE   AVAILABLE   AGE
alertmanager        1/1     1            1           114s
basic-auth-plugin   1/1     1            1           114s
faas-idler          1/1     1            1           114s
gateway             1/1     1            1           114s
nats                1/1     1            1           114s
prometheus          1/1     1            1           114s
queue-worker        1/1     1            1           114s

Reprehendo functionality:

$ kubectl rollout status -n openfaas deploy/gateway
deployment "gateway" successfully rolled out
$ kubectl port-forward -n openfaas svc/gateway 8080:8080 &
[1] 6985
Forwarding from 127.0.0.1:8080 -> 8080
$ echo -n $PASSWORD | faas-cli login --username admin --password-stdin
Calling the OpenFaaS server to validate the credentials...
Handling connection for 8080
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
credentials saved for admin http://127.0.0.1:8080
$ faas-cli list
Function                        Invocations     Replicas

installing Mongodb

Omnia gubernaculis instituimus;

$ helm repo add stable https://kubernetes-charts.storage.googleapis.com/
"stable" has been added to your repositories
$ helm install stable/mongodb --generate-name
NAME: mongodb-1577466908
LAST DEPLOYED: Fri Dec 25 11:15:11 2019
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

MongoDB can be accessed via port 27017 on the following DNS name from within your cluster:

    mongodb-1577466908.default.svc.cluster.local

To get the root password run:

    export MONGODB_ROOT_PASSWORD=$(kubectl get secret --namespace default mongodb-1577466908 -o jsonpath="{.data.mongodb-root-password}" | base64 --decode)

To connect to your database run the following command:

    kubectl run --namespace default mongodb-1577466908-client --rm --tty -i --restart='Never' --image bitnami/mongodb --command -- mongo admin --host mongodb-1577466908 --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

To connect to your database from outside the cluster execute the following commands:

    kubectl port-forward --namespace default svc/mongodb-1577466908 27017:27017 &
    mongo --host 127.0.0.1 --authenticationDatabase admin -p $MONGODB_ROOT_PASSWORD

reprehendo:

kubectl run --namespace default mongodb-1577466908-client --rm --tty -i --restart='Never' --image bitnami/mongodb --command -- mongo admin --host mongodb-1577466908 --authenticationDatabase admin -u root -p $(kubectl get secret --namespace default mongodb-1577466908 -o jsonpath="{.data.mongodb-root-password}" | base64 --decode)
If you don't see a command prompt, try pressing enter.

> db.version();
4.0.14

Press accidit + D exire continens.

Erexerit emacs

In principio omnia iam secundum se configurata sunt hoc articulumsic non singillatim ingrediar.

Perrumpi ludum in munera

Commercium cum functionibus per http protocollum exercetur, finis-ad-finem authenticas inter diversas functiones providetur a JWT. Mongodb signa thesaurizare adhibetur, sicut ludus status, notitia lusoria, series motuum omnium ludorum et alia indicia. Propius inspiciamus maxime interesting lineamenta.

Register

Initus huius functionis JSON cum ludo agnomen et tessera est. Cum hoc munus vocatur, cohibetur hanc alias in datorum non esse: si perscriptio succedit, alias tesserae Nullam in datorum inseruntur. Registration requiritur ut in ludo actuose participet.

ingressum

Munus initus est JSON cum lusu agnomen et tessera, si agnomen in datorum et tesserarum feliciter verificatur cum eo qui antea servatus est in datorum datorum, redditur JWT, quod ad alias functiones transeundum cum sunt. vocati. Variae servitutis monumenta etiam in datorum inseruntur, exempli gratia, ultimo tempore login, etc.

View a list of games

Quilibet usor non legitimus potest petere album omnium ludorum praeter activas. Usor ordinarius etiam indicem ludorum activorum videt. Effectus functionis est JSON continens tabulas ludorum (ludus ID, nomen humano-readabile, etc.).

Ludus creationis

Munus solum cum auctoritate utentium operatur, maximus numerus lusorum accipitur in initus, ac parametri ludus (exempli gratia, quae ingenia in hoc ludo activate, maximum numerum lusorum, etc.). Separatus ludi parameter est praesentia tesserae iungendi, quae te ludos non publicos creare sinit. Defalta, ludus publicus creatur. Effectus functionis JSON est, in quo creationis successus campus, singularis ludus identifier, et alii parametri continentur.

Joining ludum

Munus solum cum usoribus authenticis operatur, initus est ludus ID eiusque tessera, si ludus publicus non est, output est JSON cum ludo parametri. Auctoritas utentis, qui ludum coniunxit, ac creator ludi, postea participes ludi vocantur.

Viewing ludum certe

Quilibet usor alienum non potest petere album eventuum pro ludis otiosis, et usor ordinarius potest accipere album eventuum pro quolibet ludo activo. Additus modulus ad functionem eventus potest esse numerus quem utens iam habet. Hoc in casu, eae tantum eventus, quae postea factae sunt, in indice reddentur. Per intervalla hoc munus deducentes, user ordinarius observat quae in ludo aguntur. Hoc munus etiam petitionem reddit actionem, quam utens respondere potest ad munus mittendi eventum ludi utendi.

Mittens ludum eventu

Munus solum ad ludum participantium operatur: possibile est ludum incipere, movere, suffragium facere, nuntium scribere, quod in indice rerum gestarum ludi monstratur, etc.
Auctoritate utentis, qui ludum incipit, partes distribuentes omnibus participantibus in ludo, etiam se, munus suum confirmare debent eodem munere utentes. Postquam omnes partes confirmatae sunt, lusus automatice permutat ad modum noctis.

Ludus statistics

Munus solum ad ludum participantium operatur, status ludi, index et numerus lusorum (cognomen), munera eorumque status (moventur vel non), ac alia indicia. Ut cum praecedente munere, omnia tantum ad ludum participantium operatur.

Periodice launched munera

Si ludus per aliquod tempus determinatum in creando ludum immissus non fuerit, ipso facto removebitur e numero ludorum activorum utens manifesta functione.

Aliud periodicum negotium est coactus commutandi ludi modus de nocte in diem et rursus ad ludos per quos hoc factum non est (exempli gratia, histrio, qui ad eventum lusum agere debet, aliqua de causa solutionem suam non misit. ).

nuntius

  • introduction
  • Constituere ambitum evolutionis, negotium in functiones perfringere
  • Backend opus
  • Operis frontend
  • CICD erigens, probatio ordinans
  • Satus iudicium ludum sessionem
  • results

Source: www.habr.com

Add a comment