Yes I've followed the steps. If I run *npm start* after the existing errors
in *npm install*, the following is produced:
ERROR Error loading /home/neoggg/lab/cloudstack/ui/vue.config.js:
ERROR ValidationError: Invalid options object. Ignore Plugin has been
initialized using an options object that does not match the API schema.
- options should be one of these:
object { resourceRegExp, contextRegExp? } | object { checkResource }
Details:
* options misses the property 'resourceRegExp'. Should be:
RegExp
-> A RegExp to test the request against.
* options misses the property 'checkResource'. Should be:
function
-> A filter function for resource and context.
ValidationError: Invalid options object. Ignore Plugin has been initialized
using an options object that does not match the API schema.
- options should be one of these:
object { resourceRegExp, contextRegExp? } | object { checkResource }
Details:
* options misses the property 'resourceRegExp'. Should be:
RegExp
-> A RegExp to test the request against.
* options misses the property 'checkResource'. Should be:
function
-> A filter function for resource and context.
at validate
(/home/neoggg/lab/cloudstack/ui/node_modules/webpack/node_modules/schema-utils/dist/validate.js:105:11)
at
/home/neoggg/lab/cloudstack/ui/node_modules/webpack/lib/util/create-schema-validation.js:16:17
at new IgnorePlugin
(/home/neoggg/lab/cloudstack/ui/node_modules/webpack/lib/IgnorePlugin.js:28:3)
at Object.<anonymous>
(/home/neoggg/lab/cloudstack/ui/vue.config.js:50:7)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js
(node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at exports.loadModule
(/home/neoggg/lab/cloudstack/ui/node_modules/@vue/cli-shared-utils/lib/module.js:79:14)
at Service.loadUserOptions
(/home/neoggg/lab/cloudstack/ui/node_modules/@vue/cli-service/lib/Service.js:330:22)
at Service.init
(/home/neoggg/lab/cloudstack/ui/node_modules/@vue/cli-service/lib/Service.js:70:30)
at Service.run
(/home/neoggg/lab/cloudstack/ui/node_modules/@vue/cli-service/lib/Service.js:215:10)
at Object.<anonymous>
(/home/neoggg/lab/cloudstack/ui/node_modules/@vue/cli-service/bin/vue-cli-service.js:36:9)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
On Mon, Feb 7, 2022 at 6:52 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> Hi Pritam,
>
> Did you follow the steps on
> https://github.com/apache/cloudstack/blob/main/ui/README.md ?
>
> -Wei
>
> On Mon, 7 Feb 2022 at 13:22, Pritam Neog <neog.geek...@gmail.com> wrote:
>
> > Hello Wei,
> > *npm install* produces the following error.
> >
> > npm ERR! code ERESOLVE
> > npm ERR! ERESOLVE unable to resolve dependency tree
> > npm ERR!
> > npm ERR! While resolving: cloudstack-ui@1.0.0
> > npm ERR! Found: vue@3.2.30
> > npm ERR! node_modules/vue
> > npm ERR! vue@"^3.2.30" from the root project
> > npm ERR!
> > npm ERR! Could not resolve dependency:
> > npm ERR! peer vue@"~2" from @fortawesome/vue-fontawesome@2.0.6
> > npm ERR! node_modules/@fortawesome/vue-fontawesome
> > npm ERR! @fortawesome/vue-fontawesome@"^2.0.6" from the root project
> > npm ERR!
> > npm ERR! Fix the upstream dependency conflict, or retry
> > npm ERR! this command with --force, or --legacy-peer-deps
> > npm ERR! to accept an incorrect (and potentially broken) dependency
> > resolution.
> >
> > Also what is the difference between *npm start* and *npm run build*. I'm
> > fairly new to Node and these are probably pretty silly questions.
> > Thanks for your time.
> >
> > On Fri, Feb 4, 2022 at 2:22 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I think it is because you use python2 not python3.
> > >
> > > You can create a docker container to run a simulator environment.
> Please
> > > refer to https://github.com/apache/cloudstack/tree/main/tools/docker
> > >
> > > I have built a docker image for cloudstack 4.16.0.0, you can try it as
> > > well:
> > >
> >
> https://hub.docker.com/repository/docker/ustcweizhou/cloudstack-simulator
> > >
> > > -Wei
> > >
> > >
> > >
> > > On Fri, 4 Feb 2022 at 06:14, Pritam Neog <neog.geek...@gmail.com>
> wrote:
> > >
> > > > Thanks Wei and yes my management server was up and running. My motive
> > was
> > > > to deploy a simulator based environment. Now when I run
> > > > *python2 tools/marvin/marvin/deployDataCenter.py -i
> > > setup/dev/advanced.cfg*
> > > > it throws the following error:
> > > >
> > > > Traceback (most recent call last):
> > > > File "tools/marvin/marvin/deployDataCenter.py", line 34, in
> <module>
> > > > from marvin.lib.utils import (random_gen)
> > > > File "/usr/local/lib/python2.7/dist-packages/marvin/lib/utils.py",
> > line
> > > > 30, in <module>
> > > > import urllib.parse
> > > > ImportError: No module named parse
> > > >
> > > > I installed marvin using pip2 so I don't know why this is happening.
> > Am I
> > > > missing something?
> > > >
> > > > On Fri, Feb 4, 2022 at 12:46 AM Wei ZHOU <ustcweiz...@gmail.com>
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > It looks like the management server is running. you can check if
> the
> > > port
> > > > > 8080 is open.
> > > > >
> > > > > for the UI, you can start it in another terminal.
> > > > >
> > > > > cd ui
> > > > > npm install
> > > > > npm start
> > > > >
> > > > > Please refer to
> > > > > https://github.com/apache/cloudstack/blob/main/ui/README.md
> > > > >
> > > > > -Wei
> > > > >
> > > > > On Thu, 3 Feb 2022 at 19:34, Pritam Neog <neog.geek...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > I've been following the Hackerbook to build cloudstack. The mgmt
> > > server
> > > > > > stucks in a loop when I run
> > > > > > *mvn -pl :cloud-client-ui jetty:run
> -Djava.net.preferIPv4Stack=true
> > > > > > -Dsimulator*
> > > > > >
> > > > > > This is the log I get and it just repeats with different
> > > AccountChecker
> > > > > and
> > > > > > logid :
> > > > > >
> > > > > > INFO [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-caef4f24)
> > > > > > (logid:3281c71b) Found 0 removed accounts to cleanup
> > > > > > INFO [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-caef4f24)
> > > > > > (logid:3281c71b) Found 0 disabled accounts to cleanup
> > > > > > INFO [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-caef4f24)
> > > > > > (logid:3281c71b) Found 0 inactive domains to cleanup
> > > > > > INFO [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-caef4f24)
> > > > > > (logid:3281c71b) Found 0 disabled projects to cleanup
> > > > > > INFO [o.a.c.e.o.NetworkOrchestrator]
> > > > (Network-Scavenger-1:ctx-8a0ebaab)
> > > > > > (logid:e90dc939) NetworkGarbageCollector uses '20' seconds for GC
> > > > > interval.
> > > > > >
> > > > > > API endpoint on Port 8080 on localhost loads default jetty layout
> > > > (while
> > > > > it
> > > > > > is still looping) with a client directory which reads 'you are in
> > dev
> > > > > mode,
> > > > > > please build using npm'
> > > > > >
> > > > > > Don't know what's causing this. Any help will be appreciated.
> > > > > >
> > > > > > Kind regards,
> > > > > >
> > > > >
> > > >
> > >
> >
>
