I didn't really understand you can you please elaborate? I'm a beginner in xCAT
can you help me?
My scenario is the following:
I have an Ubuntu computer (local host) with KVM installed. Virtual machines are
created using KVM. One master node controls the other slave nodes. So, I want
to PXE boot the slave nodes and install different operating systems depending
on the user's preferences. Keeping in mind that all of this is in one single
machine.
Can you tell me how I can achieve that? In great details please with the
associated commands.
On Mar 6, 2017, at 7:50 PM, Christian Caruthers
<ccaruth...@lenovo.com<mailto:ccaruth...@lenovo.com>> wrote:
You don't have to build the stateless image on the management node. You can use
a service node or some other surrogate running the same OS, but as far as I
know you can't build a RHEL/CentOS image on a Debian/Ubuntu host.
If you don't use stateful installs rather than stateless images, you can have
as heterogenous an environment as you like. Stateless images are somewhat
limiting.
Christian Caruthers
Lenovo Professional Services
757-289-9872
Sent from my mobile device
On Mon, Mar 6, 2017 at 10:31 AM -0500, "Nora D"
<uniqu...@live.com<mailto:uniqu...@live.com>> wrote:
What if I have one management node and several slave nodes and I want to deploy
each slave node with different OS images. How can I do that?
On Mar 6, 2017, at 6:04 PM, Christian Caruthers
<ccaruth...@lenovo.com<mailto:ccaruth...@lenovo.com>> wrote:
You would need to either build your VMs to use Ubuntu or reinstall your xcat
management node, ideally using centos 7.3. It's a good practice to use the same
OS on the stateless images as is on the xCAT management node.
Regards,
Christian Caruthers
Lenovo xESS IT Consultant
Mobile: 757-289-9872
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 4, 2017 11:12 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
When I generate the image using the following command:
genimage centos7.3-x86_64-netboot-compute
I get the following:
Generating image:
cd /opt/xcat/share/xcat/netboot/centos; ./genimage -a x86_64 -o centos7.3 -p
compute --srcdir "/install/centos7.3/x86_64" --pkglist
/opt/xcat/share/xcat/netboot/centos/compute.centos7.pkglist --otherpkgdir
"/install/post/otherpkgs/centos7.3/x86_64" --postinstall
/opt/xcat/share/xcat/netboot/centos/compute.centos7.postinstall --rootimgdir
/install/netboot/centos7.3/x86_64/compute --tempfile /tmp/xcat_genimage.4583
centos7.3-x86_64-netboot-compute
100 blocks
/opt/xcat/share/xcat/netboot/centos
100 blocks
/opt/xcat/share/xcat/netboot/centos
yum -y -c /tmp/genimage.4590.yum.conf
--installroot=/install/netboot/centos7.3/x86_64/compute/rootimg/
--disablerepo=* --enablerepo=centos7.3-x86_64-0 install bash dracut-network
nfs-utils openssl dhclient kernel openssh-server openssh-clients iputils bc
irqbalance procps-ng wget vim-minimal ntp rpm rsync rsyslog e2fsprogs parted
net-tools gzip tar xz
sh: 1: yum: not found
yum invocation failed
Error: Command failed: cd /opt/xcat/share/xcat/netboot/centos; ./genimage -a
x86_64 -o centos7.3 -p compute --srcdir "/install/centos7.3/x86_64" --pkglist
/opt/xcat/share/xcat/netboot/centos/compute.centos7.pkglist --otherpkgdir
"/install/post/otherpkgs/centos7.3/x86_64" --postinstall
/opt/xcat/share/xcat/netboot/centos/compute.centos7.postinstall --rootimgdir
/install/netboot/centos7.3/x86_64/compute --tempfile /tmp/xcat_genimage.4583
centos7.3-x86_64-netboot-compute 2>&1. Error message: 100 blocks
/opt/xcat/share/xcat/netboot/centos
100 blocks
/opt/xcat/share/xcat/netboot/centos
yum -y -c /tmp/genimage.4590.yum.conf
--installroot=/install/netboot/centos7.3/x86_64/compute/rootimg/
--disablerepo=* --enablerepo=centos7.3-x86_64-0 install bash dracut-network
nfs-utils openssl dhclient kernel openssh-server openssh-clients iputils bc
irqbalance procps-ng wget vim-minimal ntp rpm rsync rsyslog e2fsprogs parted
net-tools gzip tar xz
sh: 1: yum: not found
yum invocation failed.
I think because yum is used with redhat not Ubuntu.
How can I work around this?
________________________________
From: Nora D <uniqu...@live.com<mailto:uniqu...@live.com>>
Sent: Saturday, March 4, 2017 3:44 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Great!
I will check the link.
Thank you for your help.
Sent from my iPhone
On Mar 4, 2017, at 6:41 PM, Jarrod Johnson
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:
Did you want to do stateless? If so:
https://sourceforge.net/p/xcat/wiki/Build_and_Boot_Stateless_Images/
It’s probably easiest to let it make the VMs for you. It is possible to use
existing VMs with some work, but based on your situation, I think it’s probably
easier to go with the new vm.
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 10:24 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Thank you so much you saved my life!!!!!!!
I really appreciate it.
I noticed that it creates a new VM I thought it will power off a VM that I
created myself.
Now the rpower on/off works with no error. However, I am aiming to achieve pxe
booting on the vm. Can you help me with that please?
When I execute the following command:
nodeset vm2 osimage=centos7.3-x86_64-netboot-compute
I get the following errors:
Error: Did you run "genimage" before running "packimage"? kernel cannot be
found at /install/netboot/centos7.3/x86_64/compute/kernel on
master.cluster.com<http://master.cluster.com>
Error: Some nodes failed to set up netboot resources on server
master.cluster.com<http://master.cluster.com>, aborting
________________________________
From: Jarrod Johnson <jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>>
Sent: Saturday, March 4, 2017 2:54 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Ah, ok.
On your xCAT system as root:
cat ~/.ssh/id_rsa.pub
This will get root’s public key. This is generic ssh setup procedure to
establish secure passwordless ssh. You would want to copy that output to
clipboard or whatever is most convenient for you.
On your desktop:
Make sure .ssh exists (it probably does already)
mkdir –p /root/.ssh
Set the permissions so that only root has read write and execute (using the
octal notation for the permission mask, if you want to research chmod more you
can get an idea of how the scheme works)
chmod 700 /root/.ssh/
Edit the file /root/.ssh/authorized_keys
This is a text file, so any text editor will work. Then you can paste into the
file just like any other text file.
Chmod 600 /root/.ssh/authorized_keys
This will assure the permissions on that file are acceptable to sshd (depending
on configuration, it may refuse to read the file unless permissions are this
limited)
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 9:48 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
No I'm just a student working on a project to simulate dynamic provisioning in
an HPC environment that's why I'm using virtual machines to simulate the
environment. I am using Vagrant along with xCAT to do that.
Sent from my iPhone
On Mar 4, 2017, at 5:38 PM, Jarrod Johnson
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:
BTW, is this to evaluate xCAT for other purposes, or to do virtual machine
management specifically? It may help to understand the goal in terms of best
way to proceed.
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 9:34 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Ok I will try it. But can you please write the commands for me in a simpler way?
Because I'm so new to Linux I'm afraid I might mess things up.
I would really appreciate it.
On Mar 4, 2017, at 5:25 PM, Jarrod Johnson
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:
With or without password?
On the xcat vm, cat ~/.ssh/id_rsa.pub
Add that to ~/.ssh/authorized_keys on the desktop
If you don’t have that already, you’ll want to mkdir ~/.ssh, chmod 700 ~/.ssh,
create that file and chmod 600 ~/.ssh/authorized_keys
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 9:19 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
I was able to ssh to 10.0.0.10 but to to 192.168.122.1.
(myUsername)@10.0.0.1 <<< that was successful
(myUsername)192.168.122.1 <<< Permission denied, please try again.
Although yesterday I was able to ssh 192.168.122.1 but I don't know what
happened today I might've changed something..
________________________________
From: Jarrod Johnson <jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>>
Sent: Saturday, March 4, 2017 2:09 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Can you ssh to 10.0.0.10 or 192.168.122.1 from the virtual machine?
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 9:04 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
Still getting the same error.
I set vmhost=10.0.0.10
And vmnics=virbr2
:(?!
On Mar 4, 2017, at 5:02 PM, Nora D
<uniqu...@live.com<mailto:uniqu...@live.com>> wrote:
Nevermind "thehost" I was assuming that I could add 192.168.122.1 to the hosts
file. I removed it know and set the vmhost=192.168.122.1
On Mar 4, 2017, at 4:58 PM, Nora D
<uniqu...@live.com<mailto:uniqu...@live.com>> wrote:
Here is "ip addr" from my desktop:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether c8:2a:14:37:20:0c brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether e4:ce:8f:15:fb:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.68/24 brd 192.168.1.255 scope global dynamic wlp3s0
valid_lft 84106sec preferred_lft 84106sec
inet6 fe80::e73a:370a:d3bb:1037/64 scope link
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state
DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: virbr0-nic: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
master br1 state DOWN group default qlen 1000
link/ether 52:54:00:81:29:75 brd ff:ff:ff:ff:ff:ff
7: br1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
group default qlen 1000
link/ether 52:54:00:81:29:75 brd ff:ff:ff:ff:ff:ff
8: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether fe:54:00:1c:fb:c0 brd ff:ff:ff:ff:ff:ff
inet 192.168.121.1/24 brd 192.168.121.255 scope global virbr1
valid_lft forever preferred_lft forever
9: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group
default qlen 1000
link/ether 52:54:00:fd:f8:10 brd ff:ff:ff:ff:ff:ff
10: virbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether fe:54:00:3f:cb:cc brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 brd 10.0.0.255 scope global virbr2
valid_lft forever preferred_lft forever
11: virbr2-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
group default qlen 1000
link/ether 52:54:00:79:0c:4a brd ff:ff:ff:ff:ff:ff
18: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr1 state UNKNOWN group default qlen 1000
link/ether fe:54:00:6e:fa:04 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe6e:fa04/64 scope link
valid_lft forever preferred_lft forever
19: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr2 state UNKNOWN group default qlen 1000
link/ether fe:54:00:fb:04:c8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fefb:4c8/64 scope link
valid_lft forever preferred_lft forever
20: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr1 state UNKNOWN group default qlen 1000
link/ether fe:54:00:1c:fb:c0 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe1c:fbc0/64 scope link
valid_lft forever preferred_lft forever
21: vnet3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr2 state UNKNOWN group default qlen 1000
link/ether fe:54:00:94:74:6b brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe94:746b/64 scope link
valid_lft forever preferred_lft forever
22: vnet4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr1 state UNKNOWN group default qlen 1000
link/ether fe:54:00:b6:a8:b6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:feb6:a8b6/64 scope link
valid_lft forever preferred_lft forever
23: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master
virbr2 state UNKNOWN group default qlen 1000
link/ether fe:54:00:3f:cb:cc brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe3f:cbcc/64 scope link
valid_lft forever preferred_lft forever
And here's from my virtual machine:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether 52:54:00:1c:fb:c0 brd ff:ff:ff:ff:ff:ff
inet 192.168.121.153/24 brd 192.168.121.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe1c:fbc0/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether 52:54:00:94:74:6b brd ff:ff:ff:ff:ff:ff
inet 10.0.0.10/24 brd 10.0.0.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe94:746b/64 scope link
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state
DOWN group default
link/ether 6e:3e:9c:b1:5c:77 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
And here's the "lsdef vm2":
root@master:~# lsdef vm2
Object name: vm2
groups=compute,all
installnic=mac
mac=52:54:00:fb:04:c8
mgt=kvm
netboot=pxe
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
primarynic=mac
serialport=0
serialspeed=115200
vmcpus=2
vmhost=thehost
vmmemory=1024
vmnicnicmodel=virtio
vmnics=virbr0
________________________________
From: Jarrod Johnson <jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>>
Sent: Saturday, March 4, 2017 1:38 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
On the desktop system, run ip addr
Also run it inside the virtual machine.
There should be an address that starts with the same bytes. Use the value from
the desktop as ‘vm.host’
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 8:35 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
How can I do that?
On Mar 4, 2017, at 4:26 PM, Jarrod Johnson
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:
What is the address of your desktop relative to the xcat master?
xCAT master reaching out to 127.0.0.1 will address the virtual machine itself,
rather than your desktop.
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 8:21 AM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
I didn't get your answer can you elaborate please what should I do?
I have xCAT on a master VM not on the hypervisor which is my localhost machine.
The issue is frustrating me please help me.
Sent from my iPhone
On Mar 4, 2017, at 4:18 PM, Jarrod Johnson
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:
Nodels vm2 vm.host
Note you do not need xcat on the hypervisors, you anly need it in one place.
From: Nora D [mailto:uniqu...@live.com]
Sent: Saturday, March 04, 2017 2:56 AM
To: xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>
Subject: [xcat-user] vm2: Error: Cannot communicate via libvirt to 127.0.0.1
I have Ubuntu 16 LTS (Desktop) as my local host machine. I installed KVM to
create virtual machines.
I have 3 virtual machines; one of them is acting as a master node to control
the other slave nodes (xCAT installed in the master node to control the slaves).
When I try to rpower off a slave node from the master node, the following error
occurs:
vm2: Error: Cannot communicate via libvirt to 127.0.0.1
When I researched there were many probabilities that may cause the issue:
unauthorized ssh, firewall, ports, etc.
I tried a lot of things but I felt lost and I'm just a beginner to the
open-source world. Can someone help me please with exact details and specific
commands?
Also, is there any way that I can reset my libvirt settings to the default
settings? Because I think I messed up some stuff which made the libvirt service
won't start.
Please help me ASAP.
Thanks.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org<http://SlashDot.org>! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
