Change package name to proc-factory, bump version to 1.8.1

Author: vgreiner

CHANGELOG.md

@@ -1,6 +1,9 @@
 
 # Change Log
 
+## 1.8.1
+- Change the package name from `processing-factory` to `proc-factory`
+
 ## 1.8.0
 - Add a /metrics endpoint that returns the service version, lock state & jobs progress
 - Add a docker HEALTHCHECK

Makefile

@@ -27,11 +27,11 @@ build-whl:
 	rm -rf pesto-cli/dist/
 	cd pesto-cli && python3 setup.py bdist_wheel
 	mkdir -p ~/.pesto/dist/
-	cp -f pesto-cli/dist/processing_factory*.whl ~/.pesto/dist/
+	cp -f pesto-cli/dist/proc_factory*.whl ~/.pesto/dist/
 	rm -rf pesto-cli/build
 
 install: uninstall build-whl
-	$(PIP) install ~/.pesto/dist/processing_factory*.whl
+	$(PIP) install ~/.pesto/dist/proc_factory*.whl
 
 install-dev: uninstall
 	cd pesto-cli && $(PIP) install -e .
@@ -44,7 +44,7 @@ clean:
 	cd pesto-cli && rm -rf build dist *egg-info .eggs .pytest_cache
 
 uninstall:
-	$(PIP) uninstall processing-factory -y
+	$(PIP) uninstall proc-factory -y
 
 test:
 	rm -rf /tmp/pesto/service-template-test

pesto-cli/docs/deploy_web_service.md

@@ -30,7 +30,7 @@ curl http://localhost:4000/api/v1/describe
 
 !!! Example
     ```json
-    {"name":"algo-service","resources":{"cpu":4,"gpu":0,"ram":8},"title":"algo-service","description":"Pesto Template contains all the boilerplate you need to create a processing-factory project","asynchronous":false,"email":"pesto@airbus.com","organization":"pesto","family":"detection","version":"1.0.0.dev0","keywords":["detection"],"template":"object-detection","config":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Geo Process API config schema for algo-service","properties":{"padding":{"description":"Padding / border needed to process the tile. 0 for no padding.","maximum":256,"minimum":0,"type":"number"},"zoom":{"description":"Zoom levels that can be processed","items":{"maximum":17,"minimum":1,"type":"number"},"minItems":1,"type":"array"}},"required":["zoom","padding"],"title":"tile-object-detection-config","type":"object"},"input":{"$schema":"http://json-schema.org/draft-06/schema#","title":"","type":"object","description":"Expected format","definition":{},"definitions":{"Image":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Image to process : it can be an url or the raw bytes encoded in base64","type":"string"},"Images":{"items":{"$ref":"#/definitions/Image"},"type":"array"},"Metadata":{"type":"object"},"Metadatas":{"items":{"$ref":"#/definitions/Metadata"},"type":"array"},"Polygon":{"$schema":"http://json-schema.org/draft-06/schema#","description":"GeoJSON Polygon","properties":{"bbox":{"items":{"type":"number"},"minItems":4,"type":"array"},"coordinates":{"items":{"items":{"items":{"type":"number"},"minItems":2,"type":"array"},"minItems":4,"type":"array"},"type":"array"},"type":{"enum":["Polygon"],"type":"string"}},"required":["type","coordinates"],"title":"Polygon","type":"object"},"Polygons":{"items":{"$ref":"#/definitions/Polygon"},"type":"array"}},"properties":{"dict_parameter":{"$ref":"#/definitions/Metadata","description":"A dict parameter"},"image":{"$ref":"#/definitions/Image","description":"Input image"},"integer_parameter":{"description":"A (integer) number parameter","type":"integer"},"number_parameter":{"description":"A (floating point) number parameter","type":"number"},"object_parameter":{"description":"A dict parameter with more spec, of the form {'key':'value'}","properties":{"key":{"type":"string"}},"type":"object"},"string_parameter":{"description":"A string parameter","type":"string"}},"required":["image"]},"output":{"$schema":"http://json-schema.org/draft-06/schema#","title":"","type":"object","description":"Expected format","definition":{},"definitions":{"Image":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Image to process : it can be an url or the raw bytes encoded in base64","type":"string"},"Images":{"items":{"$ref":"#/definitions/Image"},"type":"array"},"Metadata":{"type":"object"},"Metadatas":{"items":{"$ref":"#/definitions/Metadata"},"type":"array"},"Polygon":{"$schema":"http://json-schema.org/draft-06/schema#","description":"GeoJSON Polygon","properties":{"bbox":{"items":{"type":"number"},"minItems":4,"type":"array"},"coordinates":{"items":{"items":{"items":{"type":"number"},"minItems":2,"type":"array"},"minItems":4,"type":"array"},"type":"array"},"type":{"enum":["Polygon"],"type":"string"}},"required":["type","coordinates"],"title":"Polygon","type":"object"},"Polygons":{"items":{"$ref":"#/definitions/Polygon"},"type":"array"}},"properties":{"areas":{"$ref":"#/definitions/Polygons"},"dict_output":{"$ref":"#/definitions/Metadata"},"geojson":{"description":"A Geojson.FeatureCollection containing only Polygons as geometries","properties":{"features":{"items":{"$schema":"http://json-schema.org/draft-06/schema#","properties":{"geometry":{"$ref":"#/definitions/Polygon"},"properties":{"oneOf":[{"type":"null"},{"type":"object"}]},"type":{"enum":["Feature"],"type":"string"}},"required":["type","properties","geometry"],"title":"GeoJSON Feature","type":"object"},"type":"array"},"type":{"type":"string"}},"type":"object"},"image":{"$ref":"#/definitions/Image"},"image_list":{"$ref":"#/definitions/Images"},"integer_output":{"type":"integer"},"number_output":{"type":"number"},"string_output":{"type":"string"}}},"_links":{"self":{"relation":"Access to describe resource","href":"http://localhost:4000/api/v1/describe","type":"application/json","method":"GET"},"execution":{"relation":"Processing resource","href":"http://localhost:4000/api/v1/process","type":"Complex type, see output in describe content for more information","method":"POST"},"config":{"relation":"Processing configuration","href":"http://localhost:4000/api/v1/config","type":"application/json","method":"GET"},"version":{"relation":"Processing version","href":"http://localhost:4000/api/v1/version","type":"application/json","method":"GET"},"health":{"relation":"Processing health","href":"http://localhost:4000/api/v1/health","type":"text/plain","method":"GET"}}}
+    {"name":"algo-service","resources":{"cpu":4,"gpu":0,"ram":8},"title":"algo-service","description":"Pesto Template contains all the boilerplate you need to create a proc-factory project","asynchronous":false,"email":"pesto@airbus.com","organization":"pesto","family":"detection","version":"1.0.0.dev0","keywords":["detection"],"template":"object-detection","config":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Geo Process API config schema for algo-service","properties":{"padding":{"description":"Padding / border needed to process the tile. 0 for no padding.","maximum":256,"minimum":0,"type":"number"},"zoom":{"description":"Zoom levels that can be processed","items":{"maximum":17,"minimum":1,"type":"number"},"minItems":1,"type":"array"}},"required":["zoom","padding"],"title":"tile-object-detection-config","type":"object"},"input":{"$schema":"http://json-schema.org/draft-06/schema#","title":"","type":"object","description":"Expected format","definition":{},"definitions":{"Image":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Image to process : it can be an url or the raw bytes encoded in base64","type":"string"},"Images":{"items":{"$ref":"#/definitions/Image"},"type":"array"},"Metadata":{"type":"object"},"Metadatas":{"items":{"$ref":"#/definitions/Metadata"},"type":"array"},"Polygon":{"$schema":"http://json-schema.org/draft-06/schema#","description":"GeoJSON Polygon","properties":{"bbox":{"items":{"type":"number"},"minItems":4,"type":"array"},"coordinates":{"items":{"items":{"items":{"type":"number"},"minItems":2,"type":"array"},"minItems":4,"type":"array"},"type":"array"},"type":{"enum":["Polygon"],"type":"string"}},"required":["type","coordinates"],"title":"Polygon","type":"object"},"Polygons":{"items":{"$ref":"#/definitions/Polygon"},"type":"array"}},"properties":{"dict_parameter":{"$ref":"#/definitions/Metadata","description":"A dict parameter"},"image":{"$ref":"#/definitions/Image","description":"Input image"},"integer_parameter":{"description":"A (integer) number parameter","type":"integer"},"number_parameter":{"description":"A (floating point) number parameter","type":"number"},"object_parameter":{"description":"A dict parameter with more spec, of the form {'key':'value'}","properties":{"key":{"type":"string"}},"type":"object"},"string_parameter":{"description":"A string parameter","type":"string"}},"required":["image"]},"output":{"$schema":"http://json-schema.org/draft-06/schema#","title":"","type":"object","description":"Expected format","definition":{},"definitions":{"Image":{"$schema":"http://json-schema.org/draft-06/schema#","description":"Image to process : it can be an url or the raw bytes encoded in base64","type":"string"},"Images":{"items":{"$ref":"#/definitions/Image"},"type":"array"},"Metadata":{"type":"object"},"Metadatas":{"items":{"$ref":"#/definitions/Metadata"},"type":"array"},"Polygon":{"$schema":"http://json-schema.org/draft-06/schema#","description":"GeoJSON Polygon","properties":{"bbox":{"items":{"type":"number"},"minItems":4,"type":"array"},"coordinates":{"items":{"items":{"items":{"type":"number"},"minItems":2,"type":"array"},"minItems":4,"type":"array"},"type":"array"},"type":{"enum":["Polygon"],"type":"string"}},"required":["type","coordinates"],"title":"Polygon","type":"object"},"Polygons":{"items":{"$ref":"#/definitions/Polygon"},"type":"array"}},"properties":{"areas":{"$ref":"#/definitions/Polygons"},"dict_output":{"$ref":"#/definitions/Metadata"},"geojson":{"description":"A Geojson.FeatureCollection containing only Polygons as geometries","properties":{"features":{"items":{"$schema":"http://json-schema.org/draft-06/schema#","properties":{"geometry":{"$ref":"#/definitions/Polygon"},"properties":{"oneOf":[{"type":"null"},{"type":"object"}]},"type":{"enum":["Feature"],"type":"string"}},"required":["type","properties","geometry"],"title":"GeoJSON Feature","type":"object"},"type":"array"},"type":{"type":"string"}},"type":"object"},"image":{"$ref":"#/definitions/Image"},"image_list":{"$ref":"#/definitions/Images"},"integer_output":{"type":"integer"},"number_output":{"type":"number"},"string_output":{"type":"string"}}},"_links":{"self":{"relation":"Access to describe resource","href":"http://localhost:4000/api/v1/describe","type":"application/json","method":"GET"},"execution":{"relation":"Processing resource","href":"http://localhost:4000/api/v1/process","type":"Complex type, see output in describe content for more information","method":"POST"},"config":{"relation":"Processing configuration","href":"http://localhost:4000/api/v1/config","type":"application/json","method":"GET"},"version":{"relation":"Processing version","href":"http://localhost:4000/api/v1/version","type":"application/json","method":"GET"},"health":{"relation":"Processing health","href":"http://localhost:4000/api/v1/health","type":"text/plain","method":"GET"}}}
     ```
 
 ### **health**
@@ -156,4 +156,4 @@ It should be "DONE"
 curl "http://localhost:4000/api/v1/jobs/{jobID}/results"
 ```
 
-It returns the result of the packaged algorithm
+It returns the result of the packaged algorithm

pesto-cli/docs/details_conventions.md

@@ -62,7 +62,7 @@ Here is a description of the paths where PESTO could write some files :
 
 ```
 pesto-cli build :                           $HOME/.pesto/service-name/x.y.z/
-pesto-cli build requirements (local cache): $HOME/.pesto/.processing-factory-requirements/
+pesto-cli build requirements (local cache): $HOME/.pesto/.proc-factory-requirements/
 pesto-ws async jobs files :                 $HOME/.pesto/.processing/jobs/${job_id}/
 pesto-template (unit testing) :             /tmp/pesto/test
 ```

pesto-cli/docs/get_started.md

@@ -22,7 +22,7 @@ First, install PESTO-CLI in your environment as follows:
 === "Pypi"
 
     ```bash
-    $ pip install processing-factory
+    $ pip install proc-factory
     ```
 
 === "From source"
@@ -98,7 +98,7 @@ maintainer_fullname [pesto]:
 maintainer_email [pesto@airbus.com]: 
 project_name [algo-service]: 
 project_sname [algo-service]: 
-project_short_description [Pesto Template contains all the boilerplate you need to create a processing-factory project]: 
+project_short_description [Pesto Template contains all the boilerplate you need to create a proc-factory project]:
 project_version [1.0.0.dev0]: 
 
 Service generated at /tmp/pesto/algo-service

pesto-cli/docs/package_configuration.md

@@ -250,7 +250,7 @@ We then use [JSON schema](https://json-schema.org/) to validate input payloads.
 
 The `json` files contain the input/output variables name and their information (`type`/`$ref`, `description`)
 
-Default PESTO types can be found in the source code : `processing-factory/pesto-cli/pesto/cli/resources/schema/definitions.json`
+Default PESTO types can be found in the source code : `proc-factory/pesto-cli/pesto/cli/resources/schema/definitions.json`
 
 ## Requirements
 

pesto-cli/docs/package_pesto_project.md

@@ -27,7 +27,7 @@ maintainer_fullname [pesto]:
 maintainer_email [pesto@airbus.com]: 
 project_name [algo-service]: 
 project_sname [algo-service]: 
-project_short_description [Pesto Template contains all the boilerplate you need to create a processing-factory project]: 
+project_short_description [Pesto Template contains all the boilerplate you need to create a proc-factory project]:
 project_version [1.0.0.dev0]: 
 
 Service generated at /path/to/your/workspace/algo-service

pesto-cli/docs/pesto_init.md

@@ -27,7 +27,7 @@ maintainer_fullname [pesto]:
 maintainer_email [pesto@airbus.com]: 
 project_name [algo-service]: xxx-service
 project_sname [algo-service]: xxx-service
-project_short_description [Pesto Template contains all the boilerplate you need to create a processing-factory project]: 
+project_short_description [Pesto Template contains all the boilerplate you need to create a proc-factory project]:
 project_version [1.0.0.dev0]: 
 
 Service generated at /path/to/your/workspace/xxx-service
@@ -75,7 +75,7 @@ If you have many project sharing some information (your company, email, requirem
 - Copy the default template to a new place for your own template :
 
 ```bash
-$ pip show processing-factory | grep Location | awk '{print $NF}' > /tmp/pesto_site_packages.txt
+$ pip show proc-factory | grep Location | awk '{print $NF}' > /tmp/pesto_site_packages.txt
 $ cp -r `cat /tmp/pesto_site_packages.txt`/pesto_cli/resources/pesto-template /path/to/my_pesto_template
 ```
 

pesto-cli/docs/tutorial_pytorch.md

@@ -27,7 +27,7 @@ First, ensure you have PESTO installed in a python 3.6+ environment. Typically,
 To install PESTO with pip (see [Get Started](get_started.md)): 
 
 ```bash
-$ pip install processing-factory
+$ pip install proc-factory
 ``` 
 
 ## Create PESTO project
@@ -56,7 +56,7 @@ maintainer_fullname [pesto]: Computer Vision
 maintainer_email [pesto@airbus.com]: computervision@airbus.com
 project_name [algo-service]: pytorch-deployment-tutorial
 project_sname [pytorch-deployment-tutorial]:                            
-project_short_description [Pesto Template contains all the boilerplate you need to create a processing-factory project]: My first deployment with PESTO
+project_short_description [Pesto Template contains all the boilerplate you need to create a proc-factory project]: My first deployment with PESTO
 project_version [1.0.0.dev0]: 1.0.0
 [2022-12-13 17:44:24,345] 28731-INFO app::init():l44:
 Service generated at /tmp/pesto/pytorch-deployment-tutorial

pesto-cli/integrationtests/tests-all.py

@@ -21,7 +21,7 @@
 sname = "algo-service"
 version = "1.0.0.dev0"
 image_name = "{}:{}".format(sname, version)
-description = "Pesto Template contains all the boilerplate you need to create a processing-factory project"
+description = "Pesto Template contains all the boilerplate you need to create a proc-factory project"
 organization = "pesto"
 licence = "Property of pesto, all rights reserved"
 email = "pesto@airbus.com"